Triple
T29357336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cuthred of Kent |
E744480
|
entity |
| Predicate | ruledUnderOverlordshipOf |
P112817
|
FINISHED |
| Object | Coenwulf 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: Coenwulf of Mercia | Statement: [Cuthred of Kent, ruledUnderOverlordshipOf, Coenwulf of Mercia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ruledUnderOverlordshipOf Context triple: [Cuthred of Kent, ruledUnderOverlordshipOf, Coenwulf of Mercia]
-
A.
historicallyUnderRuleOf
Indicates that one entity was historically governed, controlled, or ruled by another entity during a past period.
-
B.
overlordDuringReign
chosen
Indicates that one entity served as the ruling overlord of another entity during a specified reign period.
-
C.
ruledUnderPolity
Indicates that an entity exercised rule or governance while being subordinate to, or within the authority framework of, a particular polity.
-
D.
concludedUnderRuler
Indicates that an event, agreement, or process was completed or finalized during the reign or authority of a specific ruler.
-
E.
ruledLaterBy
Indicates that one entity came under the rule, governance, or authority of another entity at a later point in time.
- 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_69f0a79aee588190b490f19d93c6e52d |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f66985cdf881909808aaca2394310d |
completed | May 2, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69f660f4f7a88190b93c60d76b86c912 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 2:13 p.m.