Triple
T38130286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clovis II |
E952199
|
entity |
| Predicate | successorInNeustria |
P202943
|
FINISHED |
| Object | Chlothar III |
—
|
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: Chlothar III | Statement: [Clovis II, successorInNeustria, Chlothar III]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorInNeustria Context triple: [Clovis II, successorInNeustria, Chlothar III]
-
A.
successorAsKingOfWestFrancia
Indicates that one person became the next king of West Francia after another person, directly following them in that royal succession.
-
B.
successorAsKingOfTheFranks
Indicates that one person became the next king of the Franks after another person.
-
C.
successorInLotharingia
Indicates that one entity is the direct successor of another in ruling or holding authority over Lotharingia.
-
D.
successorAsKingOfAustrasia
Indicates that one person became the next king of Austrasia following another person’s reign.
-
E.
predecessorInNeustria
Indicates that one entity served as the immediate predecessor of another in a position, role, or sequence specifically within the context of Neustria.
- F. None of above. chosen
Provenance (4 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_69f76f083548819082bd2bbf53c79e8e |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a00d24043e8819090cc473b6c0923d0 |
completed | May 10, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_6a00d1ec12fc81908c514ed088ef8300 |
completed | May 10, 2026, 6:43 p.m. |
| PDg | Predicate description generation | batch_6a00d23f402c8190bf49c0d4cce10b73 |
completed | May 10, 2026, 6:45 p.m. |
Created at: May 3, 2026, 4:21 p.m.