Triple
T13438292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oberkommando der Luftwaffe |
E320287
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | OKL |
E344849
|
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: OKL | Statement: [Oberkommando der Luftwaffe, abbreviation, OKL]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: OKL Context triple: [Oberkommando der Luftwaffe, abbreviation, OKL]
-
A.
OKL
chosen
OKL was the supreme command authority of Nazi Germany’s Luftwaffe, overseeing its air force operations, organization, and strategy during World War II.
-
B.
OKH
OKH (Oberkommando des Heeres) was the German Army High Command responsible for directing land operations for Nazi Germany during much of World War II.
-
C.
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.
-
D.
OKM
OKM was the abbreviation for the Oberkommando der Marine, the supreme command authority of Nazi Germany’s Kriegsmarine (navy) during World War II.
-
E.
OKJ
OKJ is the IATA airport code for Okayama Airport in Okayama Prefecture, Japan.
- 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_69d80761e6cc8190a90c844589998ecc |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaee5ec488190bd0c1e990dbd2bc2 |
completed | April 12, 2026, 2:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7399215bc8190b846906b0f081e7f |
completed | May 3, 2026, 12:03 p.m. |
Created at: April 9, 2026, 9:40 p.m.