Triple
T2525163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cross-City Line |
E56016
|
entity |
| Predicate | openingAsBrandedRoute |
P24035
|
FINISHED |
| Object | 1978 |
—
|
LITERAL FINISHED |
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: 1978 | Statement: [Cross-City Line, openingAsBrandedRoute, 1978]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingAsBrandedRoute Context triple: [Cross-City Line, openingAsBrandedRoute, 1978]
-
A.
openedRouteThrough
Indicates that one entity has created or established a passage, connection, or pathway that allows movement or access through another entity or area.
-
B.
openingSite
Indicates the location or site where an opening or access point is created, occurs, or is situated.
-
C.
openedAsThroughRoute
chosen
Indicates that a route or service began operating as a continuous through connection, rather than as separate or terminating segments.
-
D.
launchCustomer
Indicates that an entity serves as an initial or flagship customer involved in the launch or early adoption of another entity’s product, service, or initiative.
-
E.
opensInto
Indicates that one space, structure, or passage directly leads or provides access into another space or area.
- 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_69ab4a48e4f081908f1218d244608659 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd2544b4481908e105294cebdbb1f |
completed | March 7, 2026, 7:23 a.m. |
| PD | Predicate disambiguation | batch_69abd0c144b0819092f32a13c1d127e5 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:46 p.m.