Triple
T32953616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eowa of Mercia |
E843032
|
entity |
| Predicate | successorInMercianPower |
P69954
|
FINISHED |
| Object | Penda of Mercia |
—
|
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: Penda of Mercia | Statement: [Eowa of Mercia, successorInMercianPower, Penda of Mercia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorInMercianPower Context triple: [Eowa of Mercia, successorInMercianPower, Penda of Mercia]
-
A.
successorAsOverlordOfMercia
chosen
Indicates that one entity became the next ruling overlord of Mercia after another entity.
-
B.
predecessorAsKingOfBernicia
Indicates that one entity was the previous holder of the kingship of Bernicia immediately before the other entity.
-
C.
powerStatusOfMerciaDuringReign
Indicates the political or military power condition of Mercia throughout a specified ruler’s reign.
-
D.
kingInPowerMercia
Indicates that the subject is the reigning king who currently holds power over the kingdom of Mercia.
-
E.
successorInScotland
Indicates that one entity is the next holder of a role, title, or position in Scotland following another entity.
- 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_69f3494a31f481909057136e49b4fe60 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff691f5ae481908597ce245188d31c |
completed | May 9, 2026, 5:04 p.m. |
| PD | Predicate disambiguation | batch_69ff67ceeeb081909fd00cad166c4b6a |
completed | May 9, 2026, 4:58 p.m. |
Created at: May 1, 2026, 1:21 a.m.