Triple
T6696656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ciampino–G. B. Pastine International Airport |
E152766
|
entity |
| Predicate | FAA location identifier |
P420
|
FINISHED |
| Object | — |
—
|
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: — | Statement: [Ciampino–G. B. Pastine International Airport, FAA location identifier, —]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: FAA location identifier Context triple: [Ciampino–G. B. Pastine International Airport, FAA location identifier, —]
-
A.
airportCodeFAA
Indicates that an airport is identified by a specific FAA (Federal Aviation Administration) airport code.
-
B.
FAAcode
chosen
Indicates that an entity (such as an airport or facility) is associated with a specific identifying code assigned by the Federal Aviation Administration (FAA).
-
C.
ICAOcode
Indicates that an entity is identified by a specific four-letter airport or aerodrome code assigned by the International Civil Aviation Organization (ICAO).
-
D.
callsignForIATACode
Indicates that a particular airline callsign is associated with a given IATA airline code.
-
E.
airportUse
Indicates that an airport is used or utilized by a particular entity, such as an airline, organization, or service.
- 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_69c6880687b08190805278b504d1c92c |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d16897e48190b43eda2206b14d6a |
completed | March 27, 2026, 6:50 p.m. |
| PD | Predicate disambiguation | batch_69c6d089c7488190a00853fb12f53b2a |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:05 p.m.