Triple
T18882031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sion Airport |
E461850
|
entity |
| Predicate | hasICAORegionCode |
P25279
|
FINISHED |
| Object | LS |
—
|
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: LS | Statement: [Sion Airport, hasICAORegionCode, LS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasICAORegionCode Context triple: [Sion Airport, hasICAORegionCode, LS]
-
A.
ICAORegion
Indicates that an entity is located within, associated with, or governed by a specific ICAO (International Civil Aviation Organization) region.
-
B.
hasAirportCodeRegion
chosen
Indicates that an airport code is associated with, or belongs to, a specific geographic or administrative region.
-
C.
hasIATAcode
Indicates that an entity, typically a transportation facility like an airport, is associated with a specific IATA (International Air Transport Association) code.
-
D.
ICAOcode
Indicates that an entity is identified by a specific four-letter airport or aerodrome code assigned by the International Civil Aviation Organization (ICAO).
-
E.
icaoCodeType
Indicates that the relationship specifies or classifies the ICAO (International Civil Aviation Organization) code associated with an 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_69d8dcfc3430819095ee6fc0eb4c06a5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c3d2028481908af2b1560312e26c |
completed | April 20, 2026, 6:12 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e27e1481908a8da10b28f07875 |
completed | April 19, 2026, 9:39 a.m. |
Created at: April 10, 2026, 11:57 a.m.