Triple

T371049
Position Surface form Disambiguated ID Type / Status
Subject Miranda v. Arizona E8268 entity
Predicate requiredWarning P2399 FINISHED
Object Right to remain silent 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: Right to remain silent | Statement: [Miranda v. Arizona, requiredWarning, Right to remain silent]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: requiredWarning
Context triple: [Miranda v. Arizona, requiredWarning, Right to remain silent]
  • A. warnsAbout chosen
    Indicates that one entity alerts or cautions another entity about a potential danger, risk, or problem.
  • B. requiresShowing
    Indicates that one entity must be displayed or made visible as a prerequisite or condition for another entity, action, or state.
  • C. requires
    Indicates that one entity must exist, occur, or be satisfied before another entity can exist, occur, or be carried out.
  • D. mayReportTo
    Indicates that one entity is permitted or allowed to have a reporting relationship to another entity, such as an employee being allowed to report to a particular manager.
  • E. requiresNotificationFrom
    Indicates that one entity must receive a notification from another entity before or when a certain condition, event, or action occurs.
  • 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_69a2e7f2ec648190b42bc7db424f8109 completed Feb. 28, 2026, 1:04 p.m.
NER Named-entity recognition batch_69a2ebff472881909fad81d597425ea6 completed Feb. 28, 2026, 1:22 p.m.
PD Predicate disambiguation batch_69a2e960d880819084b3df4e5137a1e2 completed Feb. 28, 2026, 1:10 p.m.
Created at: Feb. 28, 2026, 1:08 p.m.