Triple
T31543510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Theuderic IV |
E804809
|
entity |
| Predicate | successorDynastyDeFacto |
P198805
|
FINISHED |
| Object | Carolingian dynasty |
—
|
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: Carolingian dynasty | Statement: [Theuderic IV, successorDynastyDeFacto, Carolingian dynasty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorDynastyDeFacto Context triple: [Theuderic IV, successorDynastyDeFacto, Carolingian dynasty]
-
A.
successorDynasty
Indicates that one dynasty directly follows and replaces another in a sequence of rule or authority.
-
B.
successorDynastyBecame
Indicates that one dynasty replaced another and formally became its successor.
-
C.
successorAsDeFactoRuler
Indicates that one entity becomes the next actual (though not necessarily officially recognized) ruler after another entity.
-
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. 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_69f348d11a048190a65eb8384a3754ac |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69ff0b6bc4a88190bf1d38c6ea26bcdc |
completed | May 9, 2026, 10:24 a.m. |
| PD | Predicate disambiguation | batch_69ff082a22f4819095ded971dbd8ea7b |
completed | May 9, 2026, 10:10 a.m. |
| PDg | Predicate description generation | batch_69ff0b6a541c8190a6fa847552f3491f |
completed | May 9, 2026, 10:24 a.m. |
Created at: April 30, 2026, 10:07 p.m.