Triple
T38147591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eadberht I of Kent |
E952659
|
entity |
| Predicate | coRulershipType |
P80350
|
FINISHED |
| Object | partitioned kingdom |
—
|
LITERAL FINISHED |
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: partitioned kingdom | Statement: [Eadberht I of Kent, coRulershipType, partitioned kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coRulershipType Context triple: [Eadberht I of Kent, coRulershipType, partitioned kingdom]
-
A.
coRulershipForm
chosen
Indicates a political arrangement in which ruling authority is shared simultaneously by two or more co-rulers rather than held by a single sovereign.
-
B.
coRulership
Indicates a relationship in which two or more entities share authority or power to rule jointly over the same domain or group.
-
C.
typeOfOverlordship
Indicates a hierarchical relationship in which one entity holds overlordship, or superior controlling authority, over another.
-
D.
rulerOf
Indicates that one entity holds governing authority or sovereignty over another entity, such as a person ruling a country or territory.
-
E.
typeOfEmpire
Indicates the specific kind or classification of empire that an entity belongs to or represents.
- 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_69f76f0a67f4819080c492f61d688fcc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcb089a8f881909aa9e722babd43f7 |
completed | May 7, 2026, 3:32 p.m. |
| PD | Predicate disambiguation | batch_69fc45666c5c8190913bd632ac0e5b84 |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:21 p.m.