Triple
T79098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ledbetter v. Goodyear Tire & Rubber Co. (2007) dissent |
E1586
|
entity |
| Predicate | opinionType |
P2165
|
FINISHED |
| Object | dissenting 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: dissenting opinion | Statement: [Ledbetter v. Goodyear Tire & Rubber Co. (2007) dissent, opinionType, dissenting opinion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opinionType Context triple: [Ledbetter v. Goodyear Tire & Rubber Co. (2007) dissent, opinionType, dissenting opinion]
-
A.
opinionBy
Indicates that a particular opinion, viewpoint, or judgment is expressed or held by a specific entity.
-
B.
languageOfOpinion
Indicates that a particular opinion is expressed or communicated in a specified language.
-
C.
decisionType
chosen
Indicates the specific category or nature of a decision associated with an entity or event.
-
D.
typeOfSupport
Indicates the kind or category of assistance, help, or backing provided in a given context.
-
E.
opposedBy
Indicates that one entity actively resists, disagrees with, or works against the actions, views, or position of 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_69a24c60d19c8190a1b6c105ca59ef5b |
completed | Feb. 28, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69a24fd16c248190a6ee4cd96c388772 |
completed | Feb. 28, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69a24eb126b48190b410b859c1be99aa |
completed | Feb. 28, 2026, 2:10 a.m. |
Created at: Feb. 28, 2026, 2:06 a.m.