Triple
T13809110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Johannes Kohl |
E331836
|
entity |
| Predicate | hasFamilyName |
P18
|
FINISHED |
| Object | Kohl |
E64832
|
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: Kohl | Statement: [Johannes Kohl, hasFamilyName, Kohl]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kohl Context triple: [Johannes Kohl, hasFamilyName, Kohl]
-
A.
Kohl
chosen
Kohl is a German surname most prominently associated with Helmut Kohl, the long-serving Chancellor of Germany who oversaw the country’s reunification.
-
B.
Nitzschka
Nitzschka is a village and district of the town of Wurzen in the Free State of Saxony, Germany.
-
C.
Kalmus
Kalmus is a surname most notably associated with Herbert Kalmus, the co-founder of the pioneering color motion picture company Technicolor.
-
D.
Falben
Falben is an alternative name for the Cumans, a medieval nomadic Turkic people who inhabited the Eurasian steppe and played a significant role in Eastern European history.
-
E.
Menzel
Menzel is a locality or district that forms part of the town of Rüthen in North Rhine-Westphalia, Germany.
- 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_69d81c59f8808190a851bc56afdc55e9 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de026eae8481908b8880635e6a9152 |
completed | April 14, 2026, 9:01 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7b08fbc348190a199c5d92e0e46be |
completed | May 3, 2026, 8:31 p.m. |
Created at: April 9, 2026, 10:12 p.m.