Triple

T32132946
Position Surface form Disambiguated ID Type / Status
Subject Middlesex Quarter Sessions E820699 entity
Predicate didNotHandle P67020 FINISHED
Object most serious capital offences 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: most serious capital offences | Statement: [Middlesex Quarter Sessions, didNotHandle, most serious capital offences]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: didNotHandle
Context triple: [Middlesex Quarter Sessions, didNotHandle, most serious capital offences]
  • A. doesNotUsuallyHandle chosen
    Indicates that an entity is generally not responsible for or typically involved in performing a particular task, role, or type of item, even if it might do so in rare or exceptional cases.
  • B. didNotHold
    Indicates that an expected event, condition, or relationship failed to occur or be valid.
  • C. didNotOverrule
    Indicates that one entity, typically a higher authority or court, chose not to overturn, reverse, or invalidate the decision or ruling made by another entity.
  • D. didNotBecome
    Indicates that an expected or potential change of state, role, or condition between entities did not occur.
  • E. didNotReturnTo
    Indicates that an entity failed or chose not to go back to a previous place, state, or situation after having left it.
  • 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_69f349039e0c819091c7a7d322e3f46d completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6b9726c848190bd8a36c32c389f2e completed May 3, 2026, 2:56 a.m.
PD Predicate disambiguation batch_69f6b6293188819080d5041ca0adb969 completed May 3, 2026, 2:42 a.m.
Created at: May 1, 2026, 12:29 a.m.