Triple

T24395344
Position Surface form Disambiguated ID Type / Status
Subject Ashwander v. Tennessee Valley Authority E615012 entity
Predicate separateOpinionType P156043 FINISHED
Object concurring opinion 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: concurring opinion | Statement: [Ashwander v. Tennessee Valley Authority, separateOpinionType, concurring opinion]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: separateOpinionType
Context triple: [Ashwander v. Tennessee Valley Authority, separateOpinionType, concurring opinion]
  • A. hasSeparateOpinions
    Indicates that the related entities hold distinct or differing views, judgments, or beliefs about a subject.
  • B. opinionBy
    Indicates that a particular opinion, viewpoint, or judgment is expressed or held by a specific entity.
  • C. pluralityOpinionBy
    Indicates that the referenced opinion is the controlling or majority view issued by a decision-making body, as opposed to concurring or dissenting opinions.
  • D. compiledOpinionsOf
    Indicates that one entity has gathered, organized, or synthesized the opinions of another entity or group into a collective form.
  • E. givesOpinionOn
    Indicates that one entity expresses a view, judgment, or evaluation about another entity or subject.
  • 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_69e2d7e509b88190a53155d4f3de45ce completed April 18, 2026, 1:01 a.m.
NER Named-entity recognition batch_69f294d69b5c81908cf6143374934f5c completed April 29, 2026, 11:31 p.m.
PD Predicate disambiguation batch_69f287c4a2b48190b80fb7a3c0e9b018 completed April 29, 2026, 10:35 p.m.
PDg Predicate description generation batch_69f28f4d978c81908310c01def2514cc completed April 29, 2026, 11:07 p.m.
Created at: April 18, 2026, 2:04 a.m.