Triple
T3305837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Otto von Lossow |
E69446
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Otto |
E134445
|
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: Otto | Statement: [Otto von Lossow, givenName, Otto]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Otto Context triple: [Otto von Lossow, givenName, Otto]
-
A.
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.
-
B.
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.
-
C.
Otto
chosen
Otto is a given name of Germanic origin commonly used across various European countries.
-
D.
Günther
Günther is a German masculine given name traditionally associated with figures of Germanic origin and culture.
-
E.
Hermann
Hermann Minkowski was a German mathematician best known for developing the geometric formulation of special relativity using four-dimensional spacetime.
- 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_69ad859f218081909458d2cebbf57565 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb0c9470881908c36c1984fdbb67b |
completed | March 8, 2026, 5:24 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b367e9e414819088ec4b05495b86e1 |
completed | March 13, 2026, 1:27 a.m. |
Created at: March 8, 2026, 3:11 p.m.