Triple
T11587926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ceawlin of Wessex |
E274800
|
entity |
| Predicate | overlordshipRegion |
P68921
|
FINISHED |
| Object | southern Britain |
—
|
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: southern Britain | Statement: [Ceawlin of Wessex, overlordshipRegion, southern Britain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: overlordshipRegion Context triple: [Ceawlin of Wessex, overlordshipRegion, southern Britain]
-
A.
historicalRegionGoverned
Indicates that a subject entity exercised governing authority over a particular historical region during a specified period.
-
B.
ruledFromRegion
Indicates that a ruling authority exercised control or governance over a domain while being based in or operating from a specific region.
-
C.
realmRuled
chosen
Indicates that one entity serves as the sovereign or governing ruler over a particular realm, territory, or domain.
-
D.
dominanceRegion
Indicates that one entity exerts primary control, influence, or priority over a defined area, range, or scope relative to others.
-
E.
settledRegion
Indicates that an entity has established a lasting presence or habitation within a particular geographic region.
- 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_69d6aae6b14c81908dc5a74bad7591f9 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d89463360c8190b91228c46bfe2e5f |
completed | April 10, 2026, 6:10 a.m. |
| PD | Predicate disambiguation | batch_69d85dcbacd0819094d4a1237055affa |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:38 p.m.