Triple
T22248925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KONP |
E549920
|
entity |
| Predicate | hasICAOCode |
P419
|
FINISHED |
| Object | KONP |
—
|
NE NERFINISHED |
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: KONP | Statement: [KONP, hasICAOCode, KONP]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: KONP Context triple: [KONP, hasICAOCode, KONP]
-
A.
KONP
chosen
KONP is the ICAO airport code for Newport Municipal Airport in Newport, Oregon, United States.
-
B.
KONM
KONM is the ICAO airport code assigned to Socorro Municipal Airport in Socorro, New Mexico, United States.
-
C.
KOP
KOP is the Indian Railways station code for Kolhapur railway station, a key rail terminus in the city of Kolhapur, Maharashtra.
-
D.
NKP
NKP is the abbreviated name for Narkompros, the Soviet People's Commissariat for Education responsible for overseeing education and cultural policy in the early USSR.
-
E.
KONT
KONT is the ICAO airport code for Ontario International Airport, a major commercial airport serving the Inland Empire region of Southern California.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e11e41d9408190bd770cf282e22753 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f138bc69d48190b185d4b8f4089922 |
completed | April 28, 2026, 10:46 p.m. |
Created at: April 16, 2026, 8:38 p.m.