Triple
T24977411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phoenix Park |
E625061
|
entity |
| Predicate | locatedOnTransportSystem |
P8428
|
FINISHED |
| Object | Nottingham Express Transit |
—
|
NE NERFINISHED |
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: Nottingham Express Transit | Statement: [Phoenix Park, locatedOnTransportSystem, Nottingham Express Transit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedOnTransportSystem Context triple: [Phoenix Park, locatedOnTransportSystem, Nottingham Express Transit]
-
A.
situatedOnTransportRoute
Indicates that one entity is located along, on, or directly adjacent to a specified transport route (such as a road, railway, or shipping lane).
-
B.
locatedInTransportArea
Indicates that an entity is situated within a designated transport-related area or zone.
-
C.
locatedInTransportCorridor
Indicates that an entity is situated within a designated transport corridor used for the movement of people or goods.
-
D.
locatedOnRouteTo
Indicates that one entity lies along the path or course taken when traveling from a starting point to a specified destination.
-
E.
partOfTransitSystem
chosen
Indicates that something is a component or segment within a larger transit or transportation system.
- F. None of above.
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_69e2ff254570819093d197b1900305ac |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 18, 2026, 6:02 a.m.