Triple
T23313740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stoneridge Investment Partners v. Scientific-Atlanta |
E590647
|
entity |
| Predicate | plaintiffType |
P26870
|
FINISHED |
| Object | institutional investor |
—
|
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: institutional investor | Statement: [Stoneridge Investment Partners v. Scientific-Atlanta, plaintiffType, institutional investor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plaintiffType Context triple: [Stoneridge Investment Partners v. Scientific-Atlanta, plaintiffType, institutional investor]
-
A.
partyTypePlaintiffs
chosen
Indicates the classification or category of the parties serving as plaintiffs in a legal action.
-
B.
litigationType
Indicates the specific category or nature of a legal dispute or court case associated with an entity or event.
-
C.
typeOfClaim
Indicates the specific category or nature of a claim being made in relation to an entity or statement.
-
D.
typeOfLaw
Indicates that one entity is a specific category or kind of law to which the other entity pertains.
-
E.
coPlaintiffWith
Indicates that two or more parties are jointly plaintiffs in the same legal case or lawsuit.
- 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_69e25d1d32188190948eb76909d1dcc3 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1977ee5d08190a9519d7867d6bef9 |
completed | April 29, 2026, 5:30 a.m. |
| PD | Predicate disambiguation | batch_69effcf8ca2c8190887d4f4656617d21 |
completed | April 28, 2026, 12:19 a.m. |
Created at: April 17, 2026, 5:06 p.m.