Triple
T20222725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lothar |
E495297
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Lotharius |
—
|
NE NERFINISHED |
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: Lotharius | Statement: [Lothar, hasVariant, Lotharius]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lotharius Context triple: [Lothar, hasVariant, Lotharius]
-
A.
Lothaire
chosen
Lothaire is a masculine given name of Germanic origin, commonly used in French-speaking regions and historically borne by medieval European nobility.
-
B.
Theodechild of Jouarre
Theodechild of Jouarre was a 7th-century Frankish noblewoman and abbess who played a key role in the early development of monastic life in Merovingian Gaul.
-
C.
Theodebald
Theodebald is a variant form of the medieval given name Theobald, historically borne by several Frankish and Germanic nobles and rulers.
-
D.
Pepin
Pepin was the eldest son of Charlemagne, known as Pepin the Hunchback, who became notable for his failed rebellion against his father and subsequent monastic exile.
-
E.
Pepin
Pepin was a Carolingian prince who ruled as King of Aquitaine in the early 9th century.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69da626cff80819097b530718a7c98b6 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66fd729548190942bcf842f03c4cd |
completed | April 20, 2026, 6:26 p.m. |
Created at: April 11, 2026, 11:39 p.m.