Triple
T31311940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carolingian civil war 840–843 |
E798485
|
entity |
| Predicate | successionClaimant |
P10495
|
FINISHED |
| Object | Lothair I |
—
|
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: Lothair I | Statement: [Carolingian civil war 840–843, successionClaimant, Lothair I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successionClaimant Context triple: [Carolingian civil war 840–843, successionClaimant, Lothair I]
-
A.
successorDynasticClaimant
Indicates that one entity is the next recognized claimant to a dynastic title, throne, or inheritance following another entity.
-
B.
successorClaimant
Indicates that one entity is the next or replacement claimant to a right, title, or claim previously held by another entity.
-
C.
dynasticClaimants
chosen
Indicates a relationship where individuals or groups assert a hereditary right to a throne, title, or ruling position within a dynasty.
-
D.
successorRuler
Indicates that one ruler directly follows another in holding a position of authority or rule.
-
E.
successorSovereign
Indicates that one entity becomes the next ruling sovereign following another entity, inheriting their position of supreme authority.
- F. None of above.
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_69f224e1932c81908fef14f7b03a10b7 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69feecf1bb248190ba30f0bb1d22ee08 |
completed | May 9, 2026, 8:14 a.m. |
| PD | Predicate disambiguation | batch_69feea5f27748190b223ee4e3ba5a678 |
completed | May 9, 2026, 8:03 a.m. |
Created at: April 29, 2026, 9:15 p.m.