Triple
T28201746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bray Head |
E716901
|
entity |
| Predicate | railwayRunsAlong |
P172134
|
FINISHED |
| Object | Dublin–Rosslare railway line |
—
|
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: Dublin–Rosslare railway line | Statement: [Bray Head, railwayRunsAlong, Dublin–Rosslare railway line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railwayRunsAlong Context triple: [Bray Head, railwayRunsAlong, Dublin–Rosslare railway line]
-
A.
railwayLine
Indicates that there is a railway line connection or route associated with or passing through the referenced entity.
-
B.
railTracks
Indicates that one entity consists of, includes, or is associated with rail tracks used for guiding trains or rail vehicles.
-
C.
railroadRunsAlongMainStreet
Indicates that a railroad line extends parallel to and in close proximity with Main Street along its course.
-
D.
isRailwayIn
Indicates that a railway is located within or passes through a specified geographic or administrative area.
-
E.
railwayLineLocation
Indicates that a railway line is located in, passes through, or is associated with a specific geographic area or place.
- F. None of above. chosen
Provenance (4 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_69efd6b826908190857e6e7dad74ed93 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f6a9603b208190b3533ea2b441514c |
completed | May 3, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f6a8de0b948190ae333e9cd99cbf6c |
completed | May 3, 2026, 1:46 a.m. |
Created at: April 27, 2026, 10:32 p.m.