Triple
T14269899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OKKK |
E353751
|
entity |
| Predicate | replacedBy |
P101
|
FINISHED |
| Object | OKBK |
E353750
|
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: OKBK | Statement: [OKKK, replacedBy, OKBK]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: OKBK Context triple: [OKKK, replacedBy, OKBK]
-
A.
OKBK
chosen
OKBK is the ICAO airport code for Kuwait International Airport, the main international gateway to Kuwait.
-
B.
BKB
BKB is the IATA airport code for Nal Airport, a regional airport serving Bikaner in the Indian state of Rajasthan.
-
C.
GOKb
GOKb is an open, community-maintained knowledgebase that provides structured metadata about electronic resources to support library collection management and discovery services.
-
D.
KOKB
KOKB is the ICAO airport code for Oceanside Municipal Airport, a public general aviation facility serving Oceanside, California.
-
E.
OKW
OKW (Oberkommando der Wehrmacht) was the German Armed Forces High Command during Nazi Germany, overseeing the strategic direction and coordination of the Wehrmacht in World War II.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d8278d25148190abf1a8c8f5f533ad |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de657fe6708190b41de48c43cff647 |
completed | April 14, 2026, 4:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd467d45c88190ac6ac280aa691591 |
completed | May 8, 2026, 2:12 a.m. |
Created at: April 10, 2026, 1:10 a.m.