Triple
T1589416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edward II of England |
E34143
|
entity |
| Predicate | reasonForDeposition |
P24494
|
FINISHED |
| Object | baronial opposition and political crisis |
—
|
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: baronial opposition and political crisis | Statement: [Edward II of England, reasonForDeposition, baronial opposition and political crisis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForDeposition Context triple: [Edward II of England, reasonForDeposition, baronial opposition and political crisis]
-
A.
statedReason
chosen
Indicates that one entity expresses or provides another entity as the explanation, justification, or motive for an action, event, or claim.
-
B.
deposedBy
Indicates that an entity has been removed from a position of power or authority by another entity.
-
C.
reasonWritten
Indicates that one entity is the reason or motivation for which another entity was written or authored.
-
D.
reasonForRelease
Indicates the cause, justification, or circumstance that led to an entity being released.
-
E.
designationReason
Indicates the reason or justification for assigning a particular designation or status to an entity.
- 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_69a885fceb2c8190b47e0f7c0aefbff0 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a93aedd45c819085843ac843d640e8 |
completed | March 5, 2026, 8:12 a.m. |
| PD | Predicate disambiguation | batch_69a907bdc19081908c84c5c0aa09e282 |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:27 p.m.