Triple
T27151797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PAO |
E682408
|
entity |
| Predicate | isBusyGeneralAviationAirport |
P161913
|
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: [PAO, isBusyGeneralAviationAirport, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBusyGeneralAviationAirport Context triple: [PAO, isBusyGeneralAviationAirport, true]
-
A.
hasGeneralAviationActivity
Indicates that an entity is involved in or supports non-commercial, private, or recreational aviation operations.
-
B.
isCivilAirport
Indicates that an airport is designated and used primarily for civilian (non-military) aviation operations.
-
C.
hasGeneralAviationFacilities
Indicates that a location or airport provides facilities and services specifically for general 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.
isOnlyInstrumentAirportOn
Indicates that the referenced airport is the only one at that location equipped and authorized for instrument flight operations.
- 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_69eefaceb2a08190b9659b7f730629f5 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f6250321088190ae3ed1dc9f2fcd03 |
completed | May 2, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69f61b40f02081909bd9c3ea73249163 |
completed | May 2, 2026, 3:41 p.m. |
| PDg | Predicate description generation | batch_69f61fa35ac48190890102c348ed81a0 |
completed | May 2, 2026, 4 p.m. |
Created at: April 27, 2026, 9:14 a.m.