Triple
T26317658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anderson v. Cryovac |
E662015
|
entity |
| Predicate | attorneyForPlaintiffs |
P160351
|
FINISHED |
| Object | Jan Schlichtmann |
—
|
NE NERFINISHED |
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: Jan Schlichtmann | Statement: [Anderson v. Cryovac, attorneyForPlaintiffs, Jan Schlichtmann]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attorneyForPlaintiffs Context triple: [Anderson v. Cryovac, attorneyForPlaintiffs, Jan Schlichtmann]
-
A.
partyTypePlaintiffs
Indicates the classification or category of the parties serving as plaintiffs in a legal action.
-
B.
attorneysAre
chosen
Indicates that one or more entities serve in the role or capacity of attorneys for another entity or within a specified context.
-
C.
coPlaintiffWith
Indicates that two or more parties are jointly plaintiffs in the same legal case or lawsuit.
-
D.
legalRepresentation
Indicates that one entity formally acts on behalf of another in legal matters, such as providing counsel, advocacy, or defense within a legal system.
-
E.
leadPlaintiffIn
Indicates that one entity serves as the primary or representative plaintiff in a legal case involving 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_69ee812e73048190aae587f1d51e5a06 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f612607c388190ab61d1ac7d18e08d |
completed | May 2, 2026, 3:04 p.m. |
| PD | Predicate disambiguation | batch_69f611a9272881909093360472be832c |
completed | May 2, 2026, 3 p.m. |
Created at: April 26, 2026, 10:26 p.m.