Triple

T7141016
Position Surface form Disambiguated ID Type / Status
Subject Tennessee General Sessions Courts (in criminal matters) E166438 entity
Predicate canAccept P31626 FINISHED
Object guilty pleas in misdemeanor cases 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: guilty pleas in misdemeanor cases | Statement: [Tennessee General Sessions Courts (in criminal matters), canAccept, guilty pleas in misdemeanor cases]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: canAccept
Context triple: [Tennessee General Sessions Courts (in criminal matters), canAccept, guilty pleas in misdemeanor cases]
  • A. canHandle chosen
    Indicates that an entity has the ability or capacity to manage, process, or deal with another entity or situation.
  • B. acceptedIn
    Indicates that something has been formally received, approved, or admitted into a particular context, group, or system.
  • C. canPass
    Indicates that one entity is able or permitted to move through, cross, or successfully traverse another entity or barrier.
  • D. canUse
    Indicates that one entity has the ability, permission, or suitability to make use of another entity or resource.
  • E. canBe
    Indicates that one entity has the potential, permission, or capability to become, perform as, or be classified as another 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_69c6888579d481909e05a8d6b81bf733 completed March 27, 2026, 1:39 p.m.
NER Named-entity recognition batch_69c6e778875c8190a5202d3efe5a842d completed March 27, 2026, 8:24 p.m.
PD Predicate disambiguation batch_69c6e1c932888190b125ca3785b18553 completed March 27, 2026, 8 p.m.
Created at: March 27, 2026, 2:45 p.m.