Triple
T4330433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hatfield, Hertfordshire, England |
E96734
|
entity |
| Predicate | hasRoadLink |
P11435
|
FINISHED |
| Object | A414 |
E365927
|
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: A414 | Statement: [Hatfield, Hertfordshire, England, hasRoadLink, A414]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: A414 Context triple: [Hatfield, Hertfordshire, England, hasRoadLink, A414]
-
A.
A414
chosen
The A414 is a major east–west road in southern England that links several Hertfordshire towns and provides an important route near Welwyn Garden City.
-
B.
A417
A417 is a major road in England that links key towns and routes in Gloucestershire and the surrounding region.
-
C.
A419
The A419 is a major road in England that links Swindon with Gloucester, serving as an important regional route in the southwest.
-
D.
A4120
A4120 is a numbered A-road in the United Kingdom that serves as a regional connector route.
-
E.
A614
The A614 is a major road in England that serves as an important regional route connecting several towns and intersecting with key highways.
- 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_69b34542fd908190b11b08faad8decfd |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3514c39748190900e13e70ed8848c |
completed | March 12, 2026, 11:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b5d09fad588190b488012b4fc6cb8c |
completed | March 14, 2026, 9:18 p.m. |
Created at: March 12, 2026, 11:13 p.m.