Triple
T1628490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mueller |
E35200
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Miller |
E5201
|
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: Miller | Statement: [Mueller, hasVariant, Miller]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Miller Context triple: [Mueller, hasVariant, Miller]
-
A.
Miller
chosen
Miller is a common English and Scottish occupational surname historically given to people who worked in grain mills.
-
B.
Smith
Smith is a common English surname borne by numerous notable individuals across diverse fields such as politics, arts, sports, and academia.
-
C.
Mill
Mill is a village in the Dutch province of North Brabant, known for its historical sites and rural character.
-
D.
Mill
Mill is a prominent surname most famously associated with John Stuart Mill, the influential 19th-century British philosopher and political economist.
-
E.
Mir
Mir is a traditional South Asian noble title historically used by rulers and aristocrats, particularly in regions such as Sindh under dynasties like the Talpurs.
- 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_69a886036bc081909ff5de16dbe5e8ea |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a909f257948190b3398fd6dc91f586 |
completed | March 5, 2026, 4:43 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad58d5acd8819090c51678ce0f63f0 |
completed | March 8, 2026, 11:09 a.m. |
Created at: March 4, 2026, 7:28 p.m.