Triple
T12528005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HLA |
E299487
|
entity |
| Predicate | airportOwnership |
P34625
|
FINISHED |
| Object | privately owned 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: privately owned airport | Statement: [HLA, airportOwnership, privately owned airport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airportOwnership Context triple: [HLA, airportOwnership, privately owned airport]
-
A.
airportOwner
chosen
Indicates that one entity owns, controls, or holds primary legal responsibility for an airport.
-
B.
operatorHeadquartersAirport
Indicates that the specified airport serves as the primary headquarters location for the operator.
-
C.
airportOfficialName
Indicates the officially designated full name of an airport as recognized by authorities or governing bodies.
-
D.
airportDesignation
Indicates that an entity is officially designated or classified as an airport.
-
E.
airlineOwnershipType
Indicates the type or nature of ownership relationship that exists between an airline and its owning 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_69d6ada5cdd48190860d9ce30aff69be |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d95f5507b481908d13cc317b7402f6 |
completed | April 10, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69d9540d7b788190a0d57b098e90e491 |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 8, 2026, 9:57 p.m.