Triple
T27926401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General Lucio Blanco International Airport |
E707847
|
entity |
| Predicate | isBorderAirport |
P163981
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [General Lucio Blanco International Airport, isBorderAirport, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBorderAirport Context triple: [General Lucio Blanco International Airport, isBorderAirport, true]
-
A.
isDomesticAirport
Indicates that an airport primarily handles flights within the same country, rather than international routes.
-
B.
isPassengerAirport
Indicates that an airport primarily serves commercial passenger air traffic rather than cargo or other specialized operations.
-
C.
isRegionalAirport
Indicates that an airport serves a specific region or local area rather than functioning as a major national or international hub.
-
D.
isInlandAirport
Indicates that an airport is located inland, away from coastal or shoreline areas.
-
E.
isOffshoreAirport
Indicates that an airport is located offshore, such as on an artificial island or platform away from the mainland.
- 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_69ef96bbf2c48190a9d0e0291457aab6 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f6416fbf4081909b0913c337927fc4 |
completed | May 2, 2026, 6:24 p.m. |
| PD | Predicate disambiguation | batch_69f63c6895f0819088655277e45859a8 |
completed | May 2, 2026, 6:03 p.m. |
| PDg | Predicate description generation | batch_69f63fd4f7448190930c723ba7cfce62 |
completed | May 2, 2026, 6:17 p.m. |
Created at: April 27, 2026, 7 p.m.