Triple
T8600929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oberkommando der Kriegsmarine |
E203671
|
entity |
| Predicate | shortName |
P43
|
FINISHED |
| Object | OKM |
E347541
|
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: OKM | Statement: [Oberkommando der Kriegsmarine, shortName, OKM]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: OKM Context triple: [Oberkommando der Kriegsmarine, shortName, OKM]
-
A.
OKM
chosen
OKM was the abbreviation for the Oberkommando der Marine, the supreme command authority of Nazi Germany’s Kriegsmarine (navy) during World War II.
-
B.
OKS
OKS is the abbreviation commonly used for the National Olympic Committee of Serbia, the body responsible for organizing the country’s participation in the Olympic Games.
-
C.
OKO
OKO is the IATA airport code for Yokota Air Base, a United States Air Force installation in western Tokyo, Japan.
-
D.
OKA
OKA is the IATA airport code for Naha Airport, the main air gateway to Okinawa, Japan.
-
E.
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.
- 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_69ca832b56948190ba751cec255308f1 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc46d8ff408190acc7cd8dc99b2689 |
completed | March 31, 2026, 10:12 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cea8e903d0819095bfa87b83c3599f |
completed | April 2, 2026, 5:35 p.m. |
Created at: March 30, 2026, 6:24 p.m.