Triple
T16517804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asmara International Airport |
E401229
|
entity |
| Predicate | handlesTrafficScope |
P123866
|
FINISHED |
| Object | international |
—
|
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: international | Statement: [Asmara International Airport, handlesTrafficScope, international]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: handlesTrafficScope Context triple: [Asmara International Airport, handlesTrafficScope, international]
-
A.
hasTrafficFunction
Indicates that an entity performs, supports, or is assigned a specific function or role related to traffic management or control.
-
B.
hasTrafficManagement
Indicates that an entity implements, uses, or is associated with systems or measures for controlling and optimizing traffic flow.
-
C.
handlesSignificantShareOfTrafficAt
Indicates that an entity is responsible for managing or processing a substantial proportion of the traffic volume at a specified location or system.
-
D.
handlesCargoTraffic
Indicates that an entity is responsible for managing or processing the movement of cargo traffic.
-
E.
regulatesTrafficBetween
Indicates that one entity controls, manages, or directs the flow of traffic occurring between two other entities or locations.
- F. None of above. chosen
Provenance (4 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_69d883838abc8190bc79cb2d41733ce2 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e7da2248190a540a5ef8686963d |
completed | April 18, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69e296995d388190b88ebe189dce890d |
completed | April 17, 2026, 8:22 p.m. |
| PDg | Predicate description generation | batch_69e2d7f97e548190a474691a152bd8e8 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 10, 2026, 5:14 a.m.