Triple
T6729062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lothar Matthäus |
E153589
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Lothar |
E495297
|
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: Lothar | Statement: [Lothar Matthäus, givenName, Lothar]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lothar Context triple: [Lothar Matthäus, givenName, Lothar]
-
A.
Lothar
chosen
Lothar is a masculine given name of Germanic origin, historically borne by various European nobles, military figures, and notable individuals.
-
B.
Lothar König
Lothar König was a German Jesuit priest and member of the anti-Nazi resistance group associated with the Kreisau Circle during World War II.
-
C.
Gerhard
Gerhard is a masculine given name of German origin, historically common in German-speaking countries.
-
D.
Eberhard
Eberhard is a German masculine given name of Old High German origin, traditionally meaning "strong boar" or "brave boar."
-
E.
Otto of Rheinfelden
Otto of Rheinfelden was an 11th-century German nobleman and duke, notable as the son of anti-king Rudolf of Rheinfelden during the Investiture Controversy in the Holy Roman Empire.
- 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_69c6880bdd68819097de8b6099992682 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d15591c8819082620d194eba3e9d |
completed | March 27, 2026, 6:49 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c742444c3081908121fb01c93551f0 |
completed | March 28, 2026, 2:51 a.m. |
Created at: March 27, 2026, 2:08 p.m.