Triple
T38021929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baldred of Kent |
E948658
|
entity |
| Predicate | realmEventuallyAbsorbedBy |
P50531
|
FINISHED |
| Object | Kingdom 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: Kingdom of Wessex | Statement: [Baldred of Kent, realmEventuallyAbsorbedBy, Kingdom of Wessex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: realmEventuallyAbsorbedBy Context triple: [Baldred of Kent, realmEventuallyAbsorbedBy, Kingdom of Wessex]
-
A.
demolishedOrAbsorbed
chosen
Indicates that one entity has ceased to exist independently because it was either physically destroyed or organizationally absorbed into another entity.
-
B.
absorbed
Indicates that one entity takes in, soaks up, or assimilates another entity or substance.
-
C.
absorbedVillage
Indicates that one village has been incorporated into, taken over by, or merged with another village, losing its separate administrative or territorial identity.
-
D.
largelyConsumedBy
Indicates that something is mostly or predominantly eaten or used up by a particular consumer or group.
-
E.
allianceAfterAbsorption
Indicates that an alliance relationship is formed between entities after one has absorbed or taken over the other.
- 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_69f76efc10448190aff5fb566b98f952 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc995dc2481908b3bd4217f8101e7 |
completed | May 6, 2026, 11:07 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ee04f08190977b7ad70fc85896 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:20 p.m.