Triple
T25784794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baze v. Rees |
E649389
|
entity |
| Predicate | pluralityOpinion |
P77991
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Baze v. Rees, pluralityOpinion, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pluralityOpinion Context triple: [Baze v. Rees, pluralityOpinion, yes]
-
A.
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.
-
B.
pluralityOpinionJusticesJoining
chosen
Indicates that certain justices joined the opinion that received the largest number of supporting votes, forming the plurality in a court decision.
-
C.
majorityOpinion
Indicates that a particular opinion is held by more than half of the relevant group or decision-making body.
-
D.
hasSeparateOpinions
Indicates that the related entities hold distinct or differing views, judgments, or beliefs about a subject.
-
E.
medicaidOpinionPluralityBy
Indicates that a plurality (largest share) of opinions or views about Medicaid is attributed to a particular group, source, or category.
- 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_69e7ab33e9308190afe415dc6f9e8876 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f5fef935a8819083bc9cefa4a72f8e |
completed | May 2, 2026, 1:41 p.m. |
| PD | Predicate disambiguation | batch_69f4938b960081909b53c074a3e0c7c2 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 22, 2026, 5:53 a.m.