Triple
T38021930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baldred of Kent |
E948658
|
entity |
| Predicate | ruledBeforeEvent |
P24450
|
FINISHED |
| Object | final absorption of Kent into Wessex |
—
|
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: final absorption of Kent into Wessex | Statement: [Baldred of Kent, ruledBeforeEvent, final absorption of Kent into Wessex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ruledBeforeEvent Context triple: [Baldred of Kent, ruledBeforeEvent, final absorption of Kent into Wessex]
-
A.
ruledOnBy
Indicates that a decision, case, or matter has been formally decided or adjudicated by a specific authority or decision-maker.
-
B.
heldBefore
chosen
Indicates that one entity possessed or maintained control of something at an earlier time than another entity or event.
-
C.
ruled in
Indicates that an authority, such as a court or judge, has made a formal decision or judgment in favor of a particular party or position.
-
D.
wasPrecededBy
Indicates that one event, state, or entity occurred or existed earlier in time than another.
-
E.
existedBeforeEvent
Indicates that the subject entity was already in existence prior to the occurrence of the specified event.
- 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.