Triple
T15378482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Paz International Airport |
E367734
|
entity |
| Predicate | focusesOnTraffic |
P52550
|
FINISHED |
| Object | domestic routes |
—
|
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 routes | Statement: [La Paz International Airport, focusesOnTraffic, domestic routes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: focusesOnTraffic Context triple: [La Paz International Airport, focusesOnTraffic, domestic routes]
-
A.
trafficFocus
chosen
Indicates a focus of attention or priority given to a particular traffic element, flow, or direction within a transportation or network context.
-
B.
roadTraffic
Indicates the presence, flow, or conditions of vehicles and movement along roads or streets.
-
C.
traffics
Indicates engaging in the buying, selling, or illicit trading of someone or something, typically as part of an ongoing commercial or criminal operation.
-
D.
drivingFocus
Indicates that one entity serves as the primary motivating force, priority, or central concern guiding another entity’s actions or decisions.
-
E.
trafficDirection
Indicates the direction in which traffic is intended or allowed to move relative to a given reference point or segment.
- 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_69d85a1551a08190ba2caea7cd51c639 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e6044488190b0499db109f7f821 |
completed | April 16, 2026, 1:41 a.m. |
| PD | Predicate disambiguation | batch_69ded27742a881909cd73cc5c7d062fd |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:19 a.m.