Triple
T1834314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Édouard |
E41029
|
entity |
| Predicate | hasVariantSpelling |
P457
|
FINISHED |
| Object | Edouard |
E41029
|
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: Edouard | Statement: [Édouard, hasVariantSpelling, Edouard]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Edouard Context triple: [Édouard, hasVariantSpelling, Edouard]
-
A.
Édouard
chosen
Édouard is the French form of the given name Edward, commonly used in French-speaking countries.
-
B.
Henri
Henri is a given name most famously associated with the French artist Henri Matisse.
-
C.
Phillippe
Phillippe is a given name and surname, typically a French-influenced variant of Philip, used for both real and fictional individuals.
-
D.
Louis Alexandre
Louis Alexandre was a French admiral and legitimized son of King Louis XIV who became the powerful Count of Toulouse in the late 17th and early 18th centuries.
-
E.
Alexandre
Alexandre is a given name of Greek origin, commonly used in French and Portuguese-speaking countries as a form of Alexander.
- 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_69a88647f9388190909bc36e795bdaec |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb02540dc819081b19a09562139cd |
completed | March 7, 2026, 4:57 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69adfb9f3354819097ce858a8706c324 |
completed | March 8, 2026, 10:43 p.m. |
Created at: March 4, 2026, 7:33 p.m.