Triple
T31178498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Railway Crescent |
E794821
|
entity |
| Predicate | routeTerminusSouth |
P93848
|
FINISHED |
| Object | New Orleans |
—
|
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 Orleans | Statement: [Southern Railway Crescent, routeTerminusSouth, New Orleans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routeTerminusSouth Context triple: [Southern Railway Crescent, routeTerminusSouth, New Orleans]
-
A.
terminusSouthNear
Indicates that the southern end or terminus of one entity is located close to another entity.
-
B.
firstPhaseTerminusSouth
Indicates that something serves as the southern endpoint or boundary of the first phase of a process, route, or project.
-
C.
terminusSouthConnection
chosen
Indicates a connection where one entity serves as the southern terminus or endpoint of another entity.
-
D.
terminusSouthState
Indicates that the southern endpoint or terminus of an entity (such as a route or line) is located in a specified state.
-
E.
roadTerminusOf
Indicates that a road ends at, or has its terminal point at, the referenced location or route.
- 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_69f69dfdda708190be290c7bec205445 |
completed | May 3, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69f69d1a37e081908d1d86b90ff502bd |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:08 p.m.