Triple
T31639102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TAG |
E807394
|
entity |
| Predicate | primaryUseOfAirport |
P131315
|
FINISHED |
| Object | commercial aviation |
—
|
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: commercial aviation | Statement: [TAG, primaryUseOfAirport, commercial aviation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryUseOfAirport Context triple: [TAG, primaryUseOfAirport, commercial aviation]
-
A.
primaryCivilAirportComponent
Indicates that one entity serves as the main civil airport component or facility associated with another entity.
-
B.
primaryUseOf
chosen
Indicates that one entity serves as the main or principal function, purpose, or application of another entity.
-
C.
mainAccessAirport
Indicates that one location serves as the primary airport providing access to another place or region.
-
D.
airportSpecialization
Indicates that an airport is specialized or designated for a particular primary function, service type, or category of operations.
-
E.
hasPrimaryAirportRole
Indicates that an entity holds the main or principal functional role associated with an airport.
- 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_69f348d892948190915f8facacb9568c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 30, 2026, 10:48 p.m.