Triple
T34173110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great North of England Railway |
E876594
|
entity |
| Predicate | builtLineBetween |
P105759
|
FINISHED |
| Object | York |
—
|
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: York | Statement: [Great North of England Railway, builtLineBetween, York]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: builtLineBetween Context triple: [Great North of England Railway, builtLineBetween, York]
-
A.
builtLine
Indicates that an entity constructed or established a particular line, such as a route, boundary, or infrastructure segment.
-
B.
connectsCitiesViaLine
chosen
Indicates a relationship where a transportation line directly links two or more cities.
-
C.
connectedLine
Indicates that two entities are joined by a continuous line or linear connection.
-
D.
yardLine
Indicates the specific position on a football field, measured in yards from a reference goal line, where a play or event occurs.
-
E.
линия
Indicates a relationship where something is a line or forms a linear connection or boundary between points or areas.
- 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_69f349ad97ac8190bf1f17417c970e64 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70fe65ff88190885d58d51c200108 |
completed | May 3, 2026, 9:05 a.m. |
| PD | Predicate disambiguation | batch_69f70f3c5bfc81908585f52e196dafe5 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:54 a.m.