Triple
T3015154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Bosworth Field |
E82318
|
entity |
| Predicate | dynasticChange |
P39883
|
FINISHED |
| Object | end of House of York rule |
—
|
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: end of House of York rule | Statement: [Battle of Bosworth Field, dynasticChange, end of House of York rule]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dynasticChange Context triple: [Battle of Bosworth Field, dynasticChange, end of House of York rule]
-
A.
dynastyChange
chosen
Indicates a transition in ruling power from one dynasty to another.
-
B.
dynasticSuccessionChangedBy
Indicates that a change or disruption has occurred in the established line of dynastic succession due to the influence or action of the related entity.
-
C.
dynasticNameChangedTo
Indicates that an entity’s dynastic name was replaced by or transitioned into a new dynastic name.
-
D.
dynasticType
Indicates the specific kind or category of dynastic relationship or succession pattern that applies between ruling entities or lineages.
-
E.
dynasticStatus
Indicates the relationship between an entity and a ruling dynasty, such as membership in, association with, or status within that dynastic line.
- 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_69ad8b1eb53481908c39bbcd1ec104b2 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9a6b37288190a6965d183ca4b08b |
completed | March 8, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69ad961a97188190809dc73430a8eda8 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3 p.m.