Triple
T20941705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LFKF |
E515736
|
entity |
| Predicate | identifiesAirportType |
P86085
|
FINISHED |
| Object | regional airport |
—
|
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: regional airport | Statement: [LFKF, identifiesAirportType, regional airport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: identifiesAirportType Context triple: [LFKF, identifiesAirportType, regional airport]
-
A.
formerAirportType
Indicates that an entity previously had a specific airport classification or type, but no longer holds that status.
-
B.
isCivilAirport
Indicates that an airport is designated and used primarily for civilian (non-military) aviation operations.
-
C.
airportTypeManaged
Indicates that an entity is responsible for managing or overseeing a particular type or category of airport.
-
D.
servesAirportType
Indicates that a transportation service or facility provides service to, or is designated for, a specific type or category of airport.
-
E.
airportTypePresent
chosen
Indicates that a specific type or category of airport is present or exists in relation to the referenced entity.
- 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_69e0b4fc13408190b06868df03c5c29b |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6f9571c448190b314a66e02772b1e |
completed | April 21, 2026, 4:13 a.m. |
| PD | Predicate disambiguation | batch_69e5c9b1bae48190a845165fed1b005e |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:50 p.m.