Triple
T19624967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oskar Potiorek |
E471110
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Oskar |
—
|
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: Oskar | Statement: [Oskar Potiorek, givenName, Oskar]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Oskar Context triple: [Oskar Potiorek, givenName, Oskar]
-
A.
Oskar
chosen
Oskar is a masculine given name of Germanic origin, commonly used in various European countries.
-
B.
Erich
Erich is a masculine given name of German origin, commonly used in German-speaking countries and beyond.
-
C.
Helmut
Helmut is a masculine given name of German origin, historically common in German-speaking countries.
-
D.
Jacob Heym
Jacob Heym is the fictional Jewish shopkeeper in a World War II ghetto who becomes a reluctant symbol of hope by spreading invented news in the story "Jacob the Liar."
-
E.
Alois
Alois is a masculine given name of Germanic origin, notably borne by Alois Hitler, the father of Adolf Hitler.
- 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_69d8e510fa248190b7afb274a1d4cf73 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e640e92ff48190ae6e6ba2c603d5e7 |
completed | April 20, 2026, 3:06 p.m. |
Created at: April 10, 2026, 1:44 p.m.