Triple
T36794832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aerovías de Integración Regional S.A. |
E909154
|
entity |
| Predicate | routeScope |
P119124
|
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: [Aerovías de Integración Regional S.A., routeScope, domestic routes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routeScope Context triple: [Aerovías de Integración Regional S.A., routeScope, domestic routes]
-
A.
routingDomainScope
Indicates the specific routing domain or context within which a route, policy, or network configuration is valid or applied.
-
B.
routeNetworkScope
chosen
Indicates the extent or coverage within a route network to which a given relationship, rule, or operation applies.
-
C.
routeContext
Indicates the contextual relationship between a route and its surrounding conditions, such as environment, constraints, or usage circumstances, under which that route is defined or applied.
-
D.
route
Indicates that one entity serves as a path or course used to travel or move between locations associated with another entity.
-
E.
routeArea
Indicates that an area is associated with, covered by, or traversed by a particular 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_69f76e7b98888190899b6478a82ad6ae |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf7890008190a8bc355ff2d61c86 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:12 p.m.