Triple
T808287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edgar Ætheling |
E17485
|
entity |
| Predicate | reignClaimStart |
P21281
|
FINISHED |
| Object | October 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: October 1066 | Statement: [Edgar Ætheling, reignClaimStart, October 1066]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reignClaimStart Context triple: [Edgar Ætheling, reignClaimStart, October 1066]
-
A.
reignStart
Indicates the date or point in time when an entity’s period of ruling or governing authority begins.
-
B.
reignAs
Indicates that an entity holds and exercises ruling authority or sovereignty over a domain or people for a period of time.
-
C.
reignStartAsKingOfPortugal
Indicates the time or event at which an individual begins their reign as the king of Portugal.
-
D.
reasonForStartOfReign
Indicates the cause, circumstance, or event that led to the beginning of an entity’s reign.
-
E.
dynasticClaim
Indicates a relationship where one party asserts a hereditary or lineage-based right to rule, inherit, or hold authority over another.
- 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.