Triple
T34430019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dundrum |
E883801
|
entity |
| Predicate | servedByTramStop |
P29999
|
FINISHED |
| Object | Dundrum Luas stop |
—
|
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: Dundrum Luas stop | Statement: [Dundrum, servedByTramStop, Dundrum Luas stop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedByTramStop Context triple: [Dundrum, servedByTramStop, Dundrum Luas stop]
-
A.
servedByTramwayLine
Indicates that a location or area is provided public transport service by a specific tramway line.
-
B.
servedByRailwayTerminus
Indicates that a place or location is provided rail transport services by a specific railway terminus.
-
C.
hasNearbyTramStop
chosen
Indicates that a location has a tram stop situated within a short walking distance or close proximity.
-
D.
connectsToMetroLineAt
Indicates that one location or transportation facility is directly linked or provides access to a specific metro line at a particular point.
-
E.
hasTramDestination
Indicates that a tram route or service goes to or terminates at a specified destination.
- 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_69f349c3dd2c819092cc9e64809f4a42 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ffa5f31c8881908c26e2aa52df6ece |
completed | May 9, 2026, 9:24 p.m. |
| PD | Predicate disambiguation | batch_69ffa42aee408190ad1a5f285688b338 |
completed | May 9, 2026, 9:16 p.m. |
Created at: May 1, 2026, 2 a.m.