Triple

T2558746
Position Surface form Disambiguated ID Type / Status
Subject Parliament of 1629 E56789 entity
Predicate endReason P24494 FINISHED
Object start of Charles I’s eleven-year Personal 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: start of Charles I’s eleven-year Personal Rule | Statement: [Parliament of 1629, endReason, start of Charles I’s eleven-year Personal Rule]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: endReason
Context triple: [Parliament of 1629, endReason, start of Charles I’s eleven-year Personal Rule]
  • A. reasonForDiscontinuation
    Indicates that one entity specifies the cause or justification for stopping, ending, or withdrawing another entity, process, or activity.
  • B. reasonForAnnulment
    Indicates the specific cause or grounds on which a prior decision, agreement, or status is formally annulled or declared invalid.
  • C. statedReason chosen
    Indicates that one entity expresses or provides another entity as the explanation, justification, or motive for an action, event, or claim.
  • D. reasonForElimination
    Indicates the specific cause or justification for why an entity was removed, disqualified, or excluded from consideration.
  • E. reasonForDecline
    Indicates the explanation or cause given for why something was rejected, reduced, or not accepted.
  • 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_69ab4a4bfec081908039988ec4c86e28 completed March 6, 2026, 9:42 p.m.
NER Named-entity recognition batch_69abd35c6ee88190b6eaa1841d3e99a4 completed March 7, 2026, 7:27 a.m.
PD Predicate disambiguation batch_69abd0caeb488190b0dd8e48d0f2777d completed March 7, 2026, 7:16 a.m.
Created at: March 6, 2026, 9:48 p.m.