Triple
T37582228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ceol of Wessex |
E935001
|
entity |
| Predicate | successorDynastyMember |
P45012
|
FINISHED |
| Object | Ceolwulf of Wessex |
—
|
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: Ceolwulf of Wessex | Statement: [Ceol of Wessex, successorDynastyMember, Ceolwulf of Wessex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorDynastyMember Context triple: [Ceol of Wessex, successorDynastyMember, Ceolwulf of Wessex]
-
A.
successorRuler
chosen
Indicates that one ruler directly follows another in holding a position of authority or rule.
-
B.
successorDynasty
Indicates that one dynasty directly follows and replaces another in a sequence of rule or authority.
-
C.
successorAsChildEmperorGuardian
Indicates that one person became the new guardian of a child emperor, succeeding another in that protective or supervisory role.
-
D.
successorDynasticClaimant
Indicates that one entity is the next recognized claimant to a dynastic title, throne, or inheritance following another entity.
-
E.
successorDynastyDeFacto
Indicates that one dynasty effectively functioned as the successor to another in practice, regardless of formal or legally recognized succession.
- 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_69f76ece61dc8190a0ab33f8d87d0a7e |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a00b03a50a88190bfb95cdcfc6142a2 |
completed | May 10, 2026, 4:20 p.m. |
| PD | Predicate disambiguation | batch_6a00afe55f248190b2cb4c7e62cc3ffc |
completed | May 10, 2026, 4:18 p.m. |
Created at: May 3, 2026, 4:17 p.m.