Triple
T9153619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Victor E. Shelford |
E219650
|
entity |
| Predicate | hasSurname |
P18
|
FINISHED |
| Object | Shelford |
E219650
|
NE FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Shelford | Statement: [Victor E. Shelford, hasSurname, Shelford]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Shelford Context triple: [Victor E. Shelford, hasSurname, Shelford]
-
A.
Shelford
chosen
Shelford is a surname most notably associated with Victor E. Shelford, an influential American zoologist and pioneer in the field of ecology.
-
B.
Shelford
Shelford is a small village in Nottinghamshire, England, known for its rural character and historic parish setting within the East Midlands.
-
C.
Shalford
Shalford is a village in Surrey, England, known for its rural character and proximity to the town of Guildford.
-
D.
SHEFFORD
SHEFFORD is a small market town in Bedfordshire, England, known for its local shops, historic buildings, and role as a service hub for surrounding villages.
-
E.
Durford
Durford is a small settlement in West Sussex, England, situated in the countryside near the River Rother.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69ca83e25418819093c6503deeaf30de |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca96e323881909cbf4d6708f24f79 |
completed | April 1, 2026, 5:13 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d04846544481909012f5c7fbbf3b0a |
completed | April 3, 2026, 11:07 p.m. |
Created at: March 30, 2026, 7:20 p.m.