Triple
T12092762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terre Haute Regional Airport |
E287987
|
entity |
| Predicate | isGeneralAviationUse |
P51772
|
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: [Terre Haute Regional Airport, isGeneralAviationUse, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isGeneralAviationUse Context triple: [Terre Haute Regional Airport, isGeneralAviationUse, true]
-
A.
hasGeneralAviationActivity
chosen
Indicates that an entity is involved in or supports non-commercial, private, or recreational aviation operations.
-
B.
hasGeneralAviationFacilities
Indicates that a location or airport provides facilities and services specifically for general aviation operations.
-
C.
aviationUsage
Indicates that something is used for, involved in, or associated with aviation-related activities or purposes.
-
D.
usedInAviation
Indicates that something is employed or applied within the field or context of aviation.
-
E.
servesAviationType
Indicates that one entity provides services or functions specifically for a particular type or category of aviation.
- 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_69d6ab4964708190850585628b287b0c |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9178ad99c8190a54777b9bbe998bc |
completed | April 10, 2026, 3:30 p.m. |
| PD | Predicate disambiguation | batch_69d915000454819089fee00022055599 |
completed | April 10, 2026, 3:19 p.m. |
Created at: April 8, 2026, 9:48 p.m.