Triple

T7204592
Position Surface form Disambiguated ID Type / Status
Subject Minersville School District v. Gobitis E148632 entity
Predicate hasDissentType P75806 FINISHED
Object solo dissent 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: solo dissent | Statement: [Minersville School District v. Gobitis, hasDissentType, solo dissent]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasDissentType
Context triple: [Minersville School District v. Gobitis, hasDissentType, solo dissent]
  • A. hasDissentAuthor
    Indicates that a decision, opinion, or ruling has an associated author who wrote a dissenting opinion.
  • B. hasDissentingJustice
    Indicates that within a judicial decision or ruling, there exists at least one justice who formally disagrees with the majority opinion.
  • C. mayDissentOn
    Indicates that an entity has the option or permission to formally disagree with or oppose another entity’s decision, opinion, or action.
  • D. dissentingJustice
    Indicates that a particular justice disagrees with the majority opinion or decision in a legal case.
  • E. standardDiscussedInDissent
    Indicates that a particular legal standard is examined or addressed within the dissenting opinion of a judicial decision.
  • F. None of above. chosen

Provenance (4 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_69c687e8cf188190b5f3ecffd681f04e completed March 27, 2026, 1:36 p.m.
NER Named-entity recognition batch_69c6e94d68ec8190ae3e1280bad12665 completed March 27, 2026, 8:32 p.m.
PD Predicate disambiguation batch_69c6e757fed4819091b0a096e3befc3a completed March 27, 2026, 8:23 p.m.
PDg Predicate description generation batch_69c6e8fd9b848190b2b1beea5698422b completed March 27, 2026, 8:30 p.m.
Created at: March 27, 2026, 2:52 p.m.