Triple
T34675560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kurumoch |
E890485
|
entity |
| Predicate | airportIATACodeNearby |
P17503
|
FINISHED |
| Object | KUF |
—
|
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: KUF | Statement: [Kurumoch, airportIATACodeNearby, KUF]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airportIATACodeNearby Context triple: [Kurumoch, airportIATACodeNearby, KUF]
-
A.
hasICAOAirportCodeNearby
Indicates that an entity is located near, or is associated with, an airport identified by a specific ICAO airport code.
-
B.
airportCodeContext
Indicates that an airport code is being used or interpreted within a specific contextual framework (such as a region, system, or standard) that defines its meaning.
-
C.
nearestAirport
Indicates that one airport is the closest in distance to a given location or entity compared to all other airports.
-
D.
airportIATAAssociated
chosen
Indicates that an airport is associated with a specific IATA (International Air Transport Association) code.
-
E.
airportLocatedNear
Indicates that an airport is situated close to a specified place or geographic feature.
- 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_69f349d9c59481908b36baa0be093aea |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f731cc6d1881908f80386ef4d70a09 |
completed | May 3, 2026, 11:30 a.m. |
| PD | Predicate disambiguation | batch_69f7317779e08190bf85777578221a6b |
completed | May 3, 2026, 11:28 a.m. |
Created at: May 1, 2026, 2:05 a.m.