Triple
T37821833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SUN COUNTRY |
E942938
|
entity |
| Predicate | operatorHubAirportICAO |
P155924
|
FINISHED |
| Object | KMSP |
E176563
|
NE 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: KMSP | Statement: [SUN COUNTRY, operatorHubAirportICAO, KMSP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatorHubAirportICAO Context triple: [SUN COUNTRY, operatorHubAirportICAO, KMSP]
-
A.
ICAOairport
Indicates that an entity is an airport identified or classified according to the ICAO (International Civil Aviation Organization) airport coding system.
-
B.
operatorMainHubAirportCountry
Indicates that an operator’s primary hub airport is located in the specified country.
-
C.
airportUse
Indicates that an airport is used or utilized by a particular entity, such as an airline, organization, or service.
-
D.
aircraftFacility
Indicates that a facility is designed, equipped, or used to support the operation, maintenance, or accommodation of aircraft.
-
E.
hasIcaoAirport
chosen
Indicates that an entity is associated with an airport identified by a specific ICAO (International Civil Aviation Organization) airport code.
- F. None of above.
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_69f76ee987588190906506e759be5db3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a0311c202408190be88a85337aacf11 |
completed | May 12, 2026, 11:40 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40f199d7588190a1f3cf894439b6fc |
completed | June 28, 2026, 10:04 a.m. |
| PD | Predicate disambiguation | batch_6a0310b0c9c88190ab218d47d4f432ed |
completed | May 12, 2026, 11:36 a.m. |
Created at: May 3, 2026, 4:19 p.m.