Triple
T17851290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karl Moser |
E445811
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Moser |
—
|
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: Moser | Statement: [Karl Moser, familyName, Moser]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Moser Context triple: [Karl Moser, familyName, Moser]
-
A.
Moser
chosen
Moser is a Norwegian surname most prominently associated with Nobel Prize–winning neuroscientists May-Britt and Edvard Moser.
-
B.
Mosser
Mosser is a small rural locality in the Allerdale district of Cumbria, England.
-
C.
Moorer
Moorer is a surname most notably associated with American former professional boxer and three-time world heavyweight champion Michael Moorer.
-
D.
Kolo Moser
Kolo Moser was an influential Austrian artist and designer associated with the Vienna Secession, known for his pioneering work in graphic design, decorative arts, and early modernist aesthetics.
-
E.
Müller
Müller is a common German surname, equivalent to "Miller" in English, historically associated with the occupation of operating a mill.
- 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_69d8b9f26f18819089c9e43250bee6ae |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e48fff6c288190a2b5e60b66c03ddc |
completed | April 19, 2026, 8:19 a.m. |
Created at: April 10, 2026, 10:17 a.m.