Triple
T1049697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Class 220 Voyager |
E22665
|
entity |
| Predicate | operatorRouteType |
P13326
|
FINISHED |
| Object | intercity services |
—
|
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: intercity services | Statement: [Class 220 Voyager, operatorRouteType, intercity services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatorRouteType Context triple: [Class 220 Voyager, operatorRouteType, intercity services]
-
A.
operationType
Indicates the specific kind of operation or action being performed or recorded in the relationship between entities.
-
B.
parentRouteType
Indicates that one route type serves as the parent or higher-level category for another route type within a route hierarchy.
-
C.
routeCategory
Indicates the classification or type assigned to a route within a transportation or path network.
-
D.
operatedOnRoute
Indicates that a transportation service or vehicle was active and provided service along a specified route.
-
E.
hasRouteType
chosen
Indicates that there is a specific kind or category of route associated with an entity (e.g., road, rail, bus line).
- 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_69a493da02e081908c13ff5e02a0fe7a |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b8b2c6208190b6fdf3e93b1b1d04 |
completed | March 1, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69a4b7309cc481908ed839b0b8d75dbf |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.