Triple
T13688258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fordstown Crossroads, County Meath, Ireland |
E328189
|
entity |
| Predicate | isJunctionPointInRoadNetwork |
P64784
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Fordstown Crossroads, County Meath, Ireland, isJunctionPointInRoadNetwork, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isJunctionPointInRoadNetwork Context triple: [Fordstown Crossroads, County Meath, Ireland, isJunctionPointInRoadNetwork, true]
-
A.
isMajorJunctionOnLine
Indicates that a location serves as a primary connecting junction along a particular line or route.
-
B.
isJunctionOnLine
chosen
Indicates that a particular junction lies on, or is part of, a specified line.
-
C.
isMajorRoadJunction
Indicates that a location serves as a primary intersection where major roads or highways meet or cross.
-
D.
isInTransportNetwork
Indicates that an entity is part of, connected to, or contained within a specific transport network or system.
-
E.
isNumberedJunctionOf
Indicates that a junction (such as a road or rail intersection) has been assigned an official identifying number within a network.
- 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_69d8076ff62081908a7bd79889edd7a0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc670968881908e2b4fdf656c7285 |
completed | April 12, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69dbbe9059488190a8113177c83e1481 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:53 p.m.