Triple
T11055007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coyle v. Smith |
E261350
|
entity |
| Predicate | courtOpinionType |
P42260
|
FINISHED |
| Object | majority 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: majority opinion | Statement: [Coyle v. Smith, courtOpinionType, majority opinion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: courtOpinionType Context triple: [Coyle v. Smith, courtOpinionType, majority opinion]
-
A.
legalCitationType
Indicates the specific kind or category of legal citation that characterizes the relationship between the citing and cited legal sources.
-
B.
typeOfAppeals
Indicates the specific category or kind of appeals associated with or applied to a given case, decision, or legal action.
-
C.
typeOfLaw
Indicates that one entity is a specific category or kind of law to which the other entity pertains.
-
D.
typeOfJurisdictionDocument
Indicates the specific kind or category of jurisdiction-related document associated with an entity or legal context.
-
E.
legalRulingNature
chosen
Indicates the type or character of a legal ruling, such as its form, basis, or procedural nature.
- 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_69d6aa98650481908609c7c56bfa7902 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d798a0890481909c1d4f9d5b23f33a |
completed | April 9, 2026, 12:16 p.m. |
| PD | Predicate disambiguation | batch_69d7440da46c8190a77380d5d747ac9c |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:26 p.m.