Triple
T1638152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Müller |
E35404
|
entity |
| Predicate | hasVariantSpelling |
P457
|
FINISHED |
| Object | Muller |
E35404
|
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: Muller | Statement: [Müller, hasVariantSpelling, Muller]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Muller Context triple: [Müller, hasVariantSpelling, Muller]
-
A.
Müller
chosen
Müller is a common German surname, equivalent to "Miller" in English, historically associated with the occupation of operating a mill.
-
B.
Millner
Millner is an English occupational surname historically associated with people who made or sold hats or millinery goods.
-
C.
Günther
Günther is a German masculine given name traditionally associated with figures of Germanic origin and culture.
-
D.
Pinsker
Pinsker is a Jewish surname most notably associated with Leo Pinsker, a 19th-century physician and early Zionist activist.
-
E.
Hammann
Hammann is a German-origin surname borne by various notable individuals in fields such as aviation, music, and academia.
- 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_69a88604618c81908b41f6429c431eb6 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a90a1ac46081909f10e793898a9911 |
completed | March 5, 2026, 4:44 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69adb5b7247c81909224f04af68c3a5d |
completed | March 8, 2026, 5:45 p.m. |
Created at: March 4, 2026, 7:28 p.m.