Triple
T6266713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edvard Moser |
E140430
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Moser |
E140430
|
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: Moser | Statement: [Edvard Moser, familyName, Moser]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Moser Context triple: [Edvard 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.
Müller
Müller is a common German surname, equivalent to "Miller" in English, historically associated with the occupation of operating a mill.
-
C.
Mölders
Mölders is a German surname most prominently associated with World War II Luftwaffe fighter ace Werner Mölders.
-
D.
Morgenstern
Morgenstern is a German surname borne by various notable figures in fields such as economics, literature, and the arts.
-
E.
Mommsen
Mommsen is a German surname most famously associated with Theodor Mommsen, the Nobel Prize–winning historian and scholar of ancient Rome.
- 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_69c008cabc4081909723e2547c9d6cc0 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0639fdad081908492c44d369df8c5 |
completed | March 22, 2026, 9:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c5e4003018819087961018dc153a91 |
completed | March 27, 2026, 1:57 a.m. |
Created at: March 22, 2026, 4:25 p.m.