Triple
T7650051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DIB |
E173224
|
entity |
| Predicate | icaoCodeOfSameAirport |
P419
|
FINISHED |
| Object | VEMN |
—
|
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: VEMN | Statement: [DIB, icaoCodeOfSameAirport, VEMN]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: icaoCodeOfSameAirport Context triple: [DIB, icaoCodeOfSameAirport, VEMN]
-
A.
ICAOcode
chosen
Indicates that an entity is identified by a specific four-letter airport or aerodrome code assigned by the International Civil Aviation Organization (ICAO).
-
B.
airportCodeFAA
Indicates that an airport is identified by a specific FAA (Federal Aviation Administration) airport code.
-
C.
successorCodeForSameAirport
Indicates that one code is the direct replacement or follow-up code for the same airport, reflecting a change while the underlying airport remains the same.
-
D.
airportIATAAssociated
Indicates that an airport is associated with a specific IATA (International Air Transport Association) code.
-
E.
airportAlsoKnownAs
Indicates that an airport is referred to by an alternative name or alias in addition to its primary name.
- 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_69c6995473348190a4f41d110d619a18 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c7061cbc3c8190a917dd7e71214182 |
completed | March 27, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69c7015dd8fc8190bc5f52a12bd46209 |
completed | March 27, 2026, 10:14 p.m. |
Created at: March 27, 2026, 3:58 p.m.