Triple
T25701574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlantic Coast Line and Tarka Line community rail route |
E644476
|
entity |
| Predicate | followsRailwayLine |
P62786
|
FINISHED |
| Object | Tarka 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: Tarka Line | Statement: [Atlantic Coast Line and Tarka Line community rail route, followsRailwayLine, Tarka Line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsRailwayLine Context triple: [Atlantic Coast Line and Tarka Line community rail route, followsRailwayLine, Tarka Line]
-
A.
followsRailroad
Indicates that one entity is aligned with or travels along the path defined by a railroad.
-
B.
railwayLine
Indicates that there is a railway line connection or route associated with or passing through the referenced entity.
-
C.
isOnRailway
chosen
Indicates that one entity is positioned on, aligned with, or traveling along a railway track or railway system in relation to another entity.
-
D.
isRailwayIn
Indicates that a railway is located within or passes through a specified geographic or administrative area.
-
E.
hasRailRoute
Indicates that there exists a rail-based transportation route or connection between the related entities.
- 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_69e77e82c9bc8190893090b2f6c64f1d |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6640168948190811bd5f933a87cf5 |
completed | May 2, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 21, 2026, 8:46 p.m.