Triple
T10006237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mill (surname) |
E198249
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Mille (surname) |
E107591
|
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: Mille (surname) | Statement: [Mill (surname), hasVariant, Mille (surname)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mille (surname) Context triple: [Mill (surname), hasVariant, Mille (surname)]
-
A.
Mill (surname)
Mill is a family name of English and Scottish origin, historically associated with people who lived or worked at a mill.
-
B.
Mille
chosen
Mille is a French surname most notably borne by individuals such as Stéphane Mille.
-
C.
Milyan
Milyan is an extinct Anatolian Indo-European language once spoken in southwestern Asia Minor, known primarily from a small corpus of inscriptions.
-
D.
Milles
Milles is a surname and variant of "Mills" that appears in English-speaking contexts.
-
E.
Milies
Milies is a traditional mountain village in Greece known for its stone architecture, rich cultural heritage, and scenic location on the slopes of Mount Pelion.
- 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_69ca830fcca48190bbbd9b20c233835f |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cdcd16afb481909a5d5893e024683f |
completed | April 2, 2026, 1:57 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d26a5d7e088190b5b1a852bfdc9073 |
completed | April 5, 2026, 1:57 p.m. |
Created at: March 30, 2026, 8:51 p.m.