Triple
T3923853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carriel Sur International Airport |
E93224
|
entity |
| Predicate | isCommercialAirport |
P49167
|
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: [Carriel Sur International Airport, isCommercialAirport, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCommercialAirport Context triple: [Carriel Sur International Airport, isCommercialAirport, true]
-
A.
isCommercialServiceAirport
chosen
Indicates that an airport is designated and operated as a commercial service facility offering scheduled passenger or cargo air transport services.
-
B.
isOnlyCommercialAirportIn
Indicates that an airport is the sole commercial airport serving a specified geographic area or region.
-
C.
isCivilAirport
Indicates that an airport is designated and used primarily for civilian (non-military) aviation operations.
-
D.
isPublicAirport
Indicates that an airport is open for use by the general public rather than restricted to private or military operations.
-
E.
isRegionalAirport
Indicates that an airport serves a specific region or local area rather than functioning as a major national or international hub.
- 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_69aed96bfa1081908f7b30f2c647dee6 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69aeed7c2c848190a6d62e2df9b942d4 |
completed | March 9, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69aee7609c4081908000ce12ae827c3f |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:23 p.m.