Triple
T30998340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Super Rapid Train |
E789865
|
entity |
| Predicate | targetRouteType |
P13416
|
FINISHED |
| Object | major intercity corridors |
—
|
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: major intercity corridors | Statement: [Super Rapid Train, targetRouteType, major intercity corridors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetRouteType Context triple: [Super Rapid Train, targetRouteType, major intercity corridors]
-
A.
parentRouteType
Indicates that one route type serves as the parent or higher-level category for another route type within a route hierarchy.
-
B.
formerRouteType
Indicates that an entity previously had a specific route classification or type, which is no longer its current status.
-
C.
hasRouteType
Indicates that there is a specific kind or category of route associated with an entity (e.g., road, rail, bus line).
-
D.
routerTypes
Indicates that one entity specifies or categorizes the types or kinds of routers associated with another entity.
-
E.
includesRouteType
chosen
Indicates that one entity’s set of routes contains or covers a specific type or category of route associated with another entity.
- 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_69f224c65a348190baaed1c01a29900c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd6dbd1b648190b1a0b391c03aebc5 |
completed | May 8, 2026, 4:59 a.m. |
| PD | Predicate disambiguation | batch_69fd6a9020548190bbfa845360ac85fb |
completed | May 8, 2026, 4:46 a.m. |
Created at: April 29, 2026, 8:56 p.m.