Triple
T6332167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Hope Airport |
E142405
|
entity |
| Predicate | hasWMOCode |
P9474
|
FINISHED |
| Object | 71263 |
—
|
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: 71263 | Statement: [Mount Hope Airport, hasWMOCode, 71263]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWMOCode Context triple: [Mount Hope Airport, hasWMOCode, 71263]
-
A.
WMO code
chosen
Indicates that an entity is associated with a specific identifier defined by the World Meteorological Organization (WMO) coding system.
-
B.
hasMeteorologicalStation
Indicates that one entity possesses, hosts, or is equipped with a meteorological station used for observing and recording weather-related data.
-
C.
hasFourLetterCode
Indicates that an entity is associated with a code consisting of exactly four characters.
-
D.
hasFAOCode
Indicates that an entity is associated with a specific FAO (Food and Agriculture Organization) code used for standardized identification in FAO classifications.
-
E.
isTropicalCycloneBasin
Indicates that a given geographic region or body of water functions as a basin where tropical cyclones can form or occur.
- 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_69c008d4d8e88190ad301c05b08722ac |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0651634b08190b54860ba0a70f5c4 |
completed | March 22, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69c060e7e2d48190af9d004236466788 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:30 p.m.