Triple
T6753350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eléonore Fabiola Victoria Anne |
E154391
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Eléonore |
E343140
|
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: Eléonore | Statement: [Eléonore Fabiola Victoria Anne, givenName, Eléonore]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Eléonore Context triple: [Eléonore Fabiola Victoria Anne, givenName, Eléonore]
-
A.
Eleonore
chosen
Eleonore is the given first name of Hannelore Kohl, the late wife of former German Chancellor Helmut Kohl.
-
B.
Yolande
Yolande is a feminine given name of French origin, commonly considered a variant of Yolanda.
-
C.
Aelinde of Amboise
Aelinde of Amboise was a medieval noblewoman known primarily as the wife of Ingelger, the founder of the House of Anjou.
-
D.
Renée
Renée is a feminine given name of French origin, commonly used in French-speaking countries and beyond.
-
E.
Éléonore de Roye
Éléonore de Roye was a 16th-century French noblewoman and influential Huguenot figure, notably serving as Countess of Roucy and a key supporter of the Protestant cause during the French Wars of Religion.
- 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_69c6880fd5808190be684854081e27dd |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d1f32fa08190bb23dc24fef14c8d |
completed | March 27, 2026, 6:52 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c70b1c4594819084716e21b16191e3 |
completed | March 27, 2026, 10:56 p.m. |
Created at: March 27, 2026, 2:11 p.m.