Triple
T13867906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ferdinand Schörner |
E333374
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Schörner |
E333374
|
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: Schörner | Statement: [Ferdinand Schörner, familyName, Schörner]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Schörner Context triple: [Ferdinand Schörner, familyName, Schörner]
-
A.
Schörner
chosen
Schörner is a German surname most notably borne by Ferdinand Schörner, a high-ranking Wehrmacht field marshal during World War II.
-
B.
Lützow
Lützow was a German heavy cruiser (originally the pocket battleship Deutschland) that served in the Kriegsmarine during World War II.
-
C.
Lützow
Lützow is a municipality in the district of Nordwestmecklenburg in the northern German state of Mecklenburg-Vorpommern.
-
D.
Hausser
Hausser is a German surname most notably associated with Paul Hausser, a high-ranking military officer of the 20th century.
-
E.
Hugo Schmeisser
Hugo Schmeisser was a German firearms designer best known for pioneering modern assault rifle concepts and influencing small arms development in the 20th century.
- 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_69d81c5ced9c8190b0e9bcc6effe5959 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de05c419d481909230e8879b6dab5c |
completed | April 14, 2026, 9:15 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7c1039128819086cfe9f966b9f142 |
completed | May 3, 2026, 9:41 p.m. |
Created at: April 9, 2026, 10:14 p.m.