Triple
T15453967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Martin-Dauch |
E371720
|
entity |
| Predicate | hasSurname |
P18
|
FINISHED |
| Object | Dauch |
E371720
|
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: Dauch | Statement: [Martin-Dauch, hasSurname, Dauch]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Dauch Context triple: [Martin-Dauch, hasSurname, Dauch]
-
A.
Dauch
chosen
Dauch is a surname of French origin borne by individuals such as Martin-Dauch.
-
B.
Dauan
Dauan is a small island in the Torres Strait of Australia, known as one of the traditional homelands of Torres Strait Islander communities.
-
C.
Neu Darchau
Neu Darchau is a small municipality in Lower Saxony, Germany, situated along the Elbe River and known for its rural character and ferry connection across the river.
-
D.
Dausa
Dausa is a town and district headquarters in the Indian state of Rajasthan, known for its historical forts, stepwells, and proximity to Jaipur.
-
E.
Echdach
Echdach was a member of the early medieval Scottish royal lineage, known primarily as a son of Áed Find, king of Dál Riata.
- 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_69d85cc8bd308190886949510b42e764 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f131b1481909ff099c3b844ee07 |
completed | April 16, 2026, 1:44 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff21b5e1788190bdc8182822f25fa1 |
completed | May 9, 2026, 11:59 a.m. |
Created at: April 10, 2026, 3:31 a.m.