Triple
T34800695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vancouver–Calgary |
E1003209
|
entity |
| Predicate | typicalRoadTravelTimeHours |
P89543
|
FINISHED |
| Object | 10–12 |
—
|
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: 10–12 | Statement: [Vancouver–Calgary, typicalRoadTravelTimeHours, 10–12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalRoadTravelTimeHours Context triple: [Vancouver–Calgary, typicalRoadTravelTimeHours, 10–12]
-
A.
travelTimeTypical
Indicates the usual or expected amount of time it takes to travel between two locations under normal conditions.
-
B.
travelTimeCategory
Indicates the qualitative classification of how long a given travel or trip duration is (e.g., short, medium, long).
-
C.
approximateDrivingTime
chosen
Indicates the estimated amount of time it takes to drive from one location to another under typical conditions.
-
D.
travelTimeAdvantage
Indicates that one option provides a shorter or more favorable travel time compared to another.
-
E.
typicalExpressBusTravelTime
Indicates the usual duration it takes for an express bus to travel between specified locations under normal conditions.
- 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_69f76db543808190b188c6c86a91491b |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fd7aac8190873077e63873aa72 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 3:59 p.m.