Triple
T7708400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alix of France, Countess of Blois |
E174681
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Alix |
E164426
|
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: Alix | Statement: [Alix of France, Countess of Blois, givenName, Alix]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Alix Context triple: [Alix of France, Countess of Blois, givenName, Alix]
-
A.
Alix
chosen
Alix is the given name of Alix of Hesse and by Rhine, who became Empress Alexandra Feodorovna of Russia as the wife of Tsar Nicholas II.
-
B.
Alexis
Alexis is a given name most famously borne by the French political thinker and historian Alexis de Tocqueville.
-
C.
Anastasie
Anastasie is the given name of Anastasie de Lafayette, a French noblewoman associated with the influential Lafayette family.
-
D.
Axelina
Axelina is a feminine given name of Scandinavian origin, used as one of the personal names of Carin Axelina Hulda Fock.
-
E.
Aline
Aline is a feminine given name of French origin, commonly used in various cultures and languages.
- 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_69c6995b3e8c8190833108f883d5f53c |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c702aadea08190bf827f5d51535224 |
completed | March 27, 2026, 10:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c8b505c7f88190ac058c1a27d758ca |
completed | March 29, 2026, 5:13 a.m. |
Created at: March 27, 2026, 4:04 p.m.