Triple
T2088443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SAN |
E32609
|
entity |
| Predicate | airportPrimaryUse |
P16381
|
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: [SAN, airportPrimaryUse, commercial aviation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airportPrimaryUse Context triple: [SAN, airportPrimaryUse, commercial aviation]
-
A.
airportRole
Indicates that an entity serves a specific functional role or capacity within the context of an airport.
-
B.
isCivilAirport
Indicates that an airport is designated and used primarily for civilian (non-military) aviation operations.
-
C.
isPublicAirport
Indicates that an airport is open for use by the general public rather than restricted to private or military operations.
-
D.
airportServesAs
chosen
Indicates that an airport functions in a particular role or capacity (such as primary, secondary, or hub) for a specified area, organization, or service.
-
E.
hubAirport
Indicates that an airport serves as a primary hub or central operating base for a particular airline or carrier.
- 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_69a885eba0708190999696a45cbec816 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abba712388819091d68a4bb99f6b17 |
completed | March 7, 2026, 5:41 a.m. |
| PD | Predicate disambiguation | batch_69abb7b4356881909217c42ccb8bb1ed |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:43 p.m.