Triple
T6992606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ingo Maurer |
E162119
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Ingo |
E239471
|
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: Ingo | Statement: [Ingo Maurer, givenName, Ingo]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ingo Context triple: [Ingo Maurer, givenName, Ingo]
-
A.
Ingo
chosen
Ingo is a given name most notably associated with architect James Ingo Freed, designer of the United States Holocaust Memorial Museum.
-
B.
Erwin
Erwin is a masculine given name of German origin, historically associated with figures such as the World War II field marshal Erwin Rommel.
-
C.
Inge
Inge is a given name of Germanic origin used in various European countries for both males and females.
-
D.
Johanus
Johanus is a given name, likely a variant or diminutive of Johan, used as a personal first name in some cultures.
-
E.
Othmar
Othmar is a masculine given name of Germanic origin, notably borne by the Swiss-American civil engineer Othmar Ammann.
- 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_69c68856d7808190ab33ee914640281b |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dbc30fdc81909244d83c8178755c |
completed | March 27, 2026, 7:34 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c76a161f088190bbc3c4e2815fa929 |
completed | March 28, 2026, 5:41 a.m. |
Created at: March 27, 2026, 2:32 p.m.