Triple
T34222193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leixlip Confey railway station |
E877950
|
entity |
| Predicate | distanceFromDublinConnolly |
P26819
|
FINISHED |
| Object | approximately 17 km |
—
|
LITERAL 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: approximately 17 km | Statement: [Leixlip Confey railway station, distanceFromDublinConnolly, approximately 17 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromDublinConnolly Context triple: [Leixlip Confey railway station, distanceFromDublinConnolly, approximately 17 km]
-
A.
distanceFromDublinCityCentre_km
chosen
Indicates the physical distance, measured in kilometers, between an entity’s location and the center of Dublin city.
-
B.
distanceFromCorkCity
Indicates the spatial distance between a given place and Cork City.
-
C.
distanceFromGalway
Indicates the spatial distance separating an entity from the location of Galway.
-
D.
distanceToDrogheda_km
Indicates the distance, measured in kilometers, between a given place or object and Drogheda.
-
E.
distanceToTullamore_km
Indicates the physical distance, measured in kilometers, between a given location and Tullamore.
- 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_69f349b16d0481908754e3069f05e0c1 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:55 a.m.