Triple
T17599283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Otto Ohlendorf |
E428651
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Otto |
—
|
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: Otto | Statement: [Otto Ohlendorf, givenName, Otto]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Otto Context triple: [Otto Ohlendorf, givenName, Otto]
-
A.
Otto
Otto is the title of one of the early nominative reports that were later incorporated into the official United States Reports, documenting decisions of the U.S. Supreme Court.
-
B.
Otto
Otto is the central German soldier protagonist in the 1993 war film "Stalingrad," whose experiences depict the brutality and futility of the Eastern Front in World War II.
-
C.
Otto
Otto is one of the official mascots created for the 2002 Winter Olympics held in Salt Lake City.
-
D.
Otto
Otto was a lesser-known medieval Polish prince from the Piast dynasty, notable mainly as a younger son of Duke Casimir I the Restorer.
-
E.
Otto
chosen
Otto is a given name of Germanic origin commonly used across various European countries.
- 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_69d889e1c6148190ba76241e74688f8b |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46c474e5481909d2736241b592dab |
completed | April 19, 2026, 5:46 a.m. |
Created at: April 10, 2026, 5:51 a.m.