Triple
T24139961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Æthelstan of Kent |
E598199
|
entity |
| Predicate | ruledUnderOverlord |
P112817
|
FINISHED |
| Object | Æthelwulf 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: Æthelwulf of Wessex | Statement: [Æthelstan of Kent, ruledUnderOverlord, Æthelwulf of Wessex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ruledUnderOverlord Context triple: [Æthelstan of Kent, ruledUnderOverlord, Æthelwulf of Wessex]
-
A.
overlordDuringReign
chosen
Indicates that one entity served as the ruling overlord of another entity during a specified reign period.
-
B.
ruledUnderPolity
Indicates that an entity exercised rule or governance while being subordinate to, or within the authority framework of, a particular polity.
-
C.
concludedUnderRuler
Indicates that an event, agreement, or process was completed or finalized during the reign or authority of a specific ruler.
-
D.
lordOf
Indicates that one entity holds lordship, authority, or dominion over another entity.
-
E.
ruledFromBehindTheThrone
Indicates that an entity exercised real governing power or control indirectly, while another, more visible figure held the official position of ruler.
- 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_69e288c92e448190ac57034fa0c863ce |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1e005f7f48190b2c538bfc79a83b2 |
completed | April 29, 2026, 10:40 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:28 p.m.