Triple
T1180133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canadian Airlines |
E25115
|
entity |
| Predicate | operatedRouteType |
P13326
|
FINISHED |
| Object | domestic |
—
|
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: domestic | Statement: [Canadian Airlines, operatedRouteType, domestic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedRouteType Context triple: [Canadian Airlines, operatedRouteType, domestic]
-
A.
operatedRoute
Indicates that a transportation service or carrier runs or manages a specific route.
-
B.
parentRouteType
Indicates that one route type serves as the parent or higher-level category for another route type within a route hierarchy.
-
C.
hasRouteType
chosen
Indicates that there is a specific kind or category of route associated with an entity (e.g., road, rail, bus line).
-
D.
notableRouteType
Indicates that a route is particularly significant or well-known for a specific type or category (e.g., scenic, historic, commercial).
-
E.
operatedOnRoute
Indicates that a transportation service or vehicle was active and provided service along a specified 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_69a494267b4c819088c97a59182bf56a |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bd53e4b48190abb2167f8074a6bc |
completed | March 1, 2026, 10:27 p.m. |
| PD | Predicate disambiguation | batch_69a4bb5844348190b01ac6506906ba3b |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:45 p.m.