Triple
T9322143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manila–Toronto |
E224293
|
entity |
| Predicate | isLongHaul |
P42175
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Manila–Toronto, isLongHaul, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLongHaul Context triple: [Manila–Toronto, isLongHaul, true]
-
A.
hasLongHaulFlights
Indicates that an entity (such as an airline, route, or airport) operates or is associated with long-distance flights typically covering intercontinental or extended-duration journeys.
-
B.
operatesLongHaulRouteFrom
Indicates that an entity (typically a transportation carrier) runs long-distance routes originating from a specified location.
-
C.
longDistanceService
chosen
Indicates that a service operates over large geographic distances, typically connecting locations that are far apart rather than nearby.
-
D.
isOnFreightRoute
Indicates that something lies along or is included within a designated freight transportation route used for moving goods.
-
E.
hasLongDistancePathAccess
Indicates that an entity has the ability or right to use a path or route that spans a long distance.
- 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_69ca8426d48481909596360f7791c7dd |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd36f2bd288190bb1556a88d9e90f3 |
completed | April 1, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69cc7a61e9a4819096eb014f3791ef2e |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:38 p.m.