Triple
T808285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edgar Ætheling |
E17485
|
entity |
| Predicate | wasProclaimed |
P21279
|
FINISHED |
| Object | king of England in 1066 |
—
|
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: king of England in 1066 | Statement: [Edgar Ætheling, wasProclaimed, king of England in 1066]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasProclaimed Context triple: [Edgar Ætheling, wasProclaimed, king of England in 1066]
-
A.
dateProclaimed
Indicates the specific date on which something was formally declared, announced, or proclaimed.
-
B.
cameToPowerIn
Indicates the time or context in which an entity assumed control, authority, or leadership over a group, organization, or territory.
-
C.
inauguratedBy
Indicates that an official event, institution, or position was formally opened, initiated, or brought into operation by a specific person or authority.
-
D.
cameToPowerAfter
Indicates that one entity assumed authority or control following the rule or tenure of another entity.
-
E.
appointedBy
Indicates that one entity has been formally selected or assigned to a position, role, or office by another entity.
- F. None of above. chosen
Provenance (4 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_69a4937ae8a08190b5084a03d532b30e |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4ac07fedc8190ab05595f25c1792f |
completed | March 1, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69a4aa7221c081908068e66fe720f26d |
completed | March 1, 2026, 9:06 p.m. |
| PDg | Predicate description generation | batch_69a4ac0688708190b62ac0a8239ec8c8 |
completed | March 1, 2026, 9:13 p.m. |
Created at: March 1, 2026, 7:38 p.m.