Triple
T20680202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rio-Sul Serviços Aéreos Regionais |
E508270
|
entity |
| Predicate | operatedRouteScope |
P18593
|
FINISHED |
| Object | regional 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: regional routes | Statement: [Rio-Sul Serviços Aéreos Regionais, operatedRouteScope, regional routes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedRouteScope Context triple: [Rio-Sul Serviços Aéreos Regionais, operatedRouteScope, regional routes]
-
A.
operatedRoute
chosen
Indicates that a transportation service or carrier runs or manages a specific route.
-
B.
laterScope
Indicates that one event, state, or condition occurs or applies after the temporal scope of another.
-
C.
parentRoute
Indicates that one route serves as the direct hierarchical ancestor or container of another route within a routing structure.
-
D.
routingDomainScope
Indicates the specific routing domain or context within which a route, policy, or network configuration is valid or applied.
-
E.
scopeChangedTo
Indicates that the scope or extent of something has been modified from its previous state to a new defined scope.
- 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_69e0b4c1164881909a3bf1e3ddb2bc32 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6bea655488190bab168d564d888af |
completed | April 21, 2026, 12:02 a.m. |
| PD | Predicate disambiguation | batch_69e5c03caee881908be4dd25796a03d5 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 11:44 a.m.