Triple
T31178497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Railway Crescent |
E794821
|
entity |
| Predicate | routeTerminusNorth |
P3375
|
FINISHED |
| Object | New York City |
—
|
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: New York City | Statement: [Southern Railway Crescent, routeTerminusNorth, New York City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routeTerminusNorth Context triple: [Southern Railway Crescent, routeTerminusNorth, New York City]
-
A.
terminusNorth
chosen
Indicates that one entity serves as the northern endpoint or final stop of another entity, such as a route, line, or path.
-
B.
roadTerminusOf
Indicates that a road ends at, or has its terminal point at, the referenced location or route.
-
C.
northSouthRoutes
Indicates that there are routes or connections running in a generally north–south direction between the related entities.
-
D.
terminusNortheast
Indicates that one entity serves as the northeastern terminus or endpoint of another entity (such as a route, line, or path).
-
E.
northernTerminusVariant
Indicates that one location or feature serves as an alternative or variant northern endpoint of a route, line, or path.
- 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_69f224d675d08190957198068e440422 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c234d648190a243fb2b107136a9 |
completed | May 3, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69f69665cd9c819088c388fc82fec42e |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:08 p.m.