Triple
T2411461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LATAM Colombia |
E52198
|
entity |
| Predicate | operatesRouteNetwork |
P5033
|
FINISHED |
| Object | Colombian domestic destinations |
—
|
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: Colombian domestic destinations | Statement: [LATAM Colombia, operatesRouteNetwork, Colombian domestic destinations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesRouteNetwork Context triple: [LATAM Colombia, operatesRouteNetwork, Colombian domestic destinations]
-
A.
operatesNetwork
chosen
Indicates that an entity manages, controls, or runs the functioning of a network.
-
B.
operatedOnRoute
Indicates that a transportation service or vehicle was active and provided service along a specified route.
-
C.
routeNetworkType
Indicates the specific kind of transportation or communication network to which a route belongs (e.g., road, rail, or air).
-
D.
transportNetwork
Indicates a relationship where infrastructure or services enable the movement of people or goods between different locations.
-
E.
associatedWithRouteNetwork
Indicates a relationship where something is linked or connected to a specific route network.
- 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_69ab495622948190bc6bc6e4cddaf645 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abc928fd608190885fcde6746a06bc |
completed | March 7, 2026, 6:43 a.m. |
| PD | Predicate disambiguation | batch_69abc5a6cbd0819086c0716e266b7ebb |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 6, 2026, 9:41 p.m.