Triple
T29702191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peada of Mercia |
E751517
|
entity |
| Predicate | ruledAfterDeathOf |
P129984
|
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: [Peada of Mercia, ruledAfterDeathOf, Penda of Mercia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ruledAfterDeathOf Context triple: [Peada of Mercia, ruledAfterDeathOf, Penda of Mercia]
-
A.
ruledLaterBy
chosen
Indicates that one entity came under the rule, governance, or authority of another entity at a later point in time.
-
B.
ruledInPlaceOf
Indicates that one entity exercised governing authority or leadership as a substitute or proxy for another entity.
-
C.
ruledDuringReignOf
Indicates that one entity exercised ruling authority or governance during the time period in which another entity’s reign took place.
-
D.
appliesAfterReignOf
Indicates that something becomes relevant, valid, or in effect only after the reign or rule of a specified entity has ended.
-
E.
executedShortlyAfterDeathOf
Indicates that one entity was executed soon after the death of another entity, with only a short time interval separating the two events.
- 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_69f0d6266f8481909e70bb41cda18587 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f672b4dba48190b1da1207a622a267 |
completed | May 2, 2026, 9:55 p.m. |
| PD | Predicate disambiguation | batch_69f66ac1a4fc81909740d2e52fbe6970 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 7:24 p.m.