Triple
T27433456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jan Schlichtmann |
E690711
|
entity |
| Predicate | opposedInCourt |
P44728
|
FINISHED |
| Object | W. R. Grace and Company |
—
|
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: W. R. Grace and Company | Statement: [Jan Schlichtmann, opposedInCourt, W. R. Grace and Company]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opposedInCourt Context triple: [Jan Schlichtmann, opposedInCourt, W. R. Grace and Company]
-
A.
opposedOnGroundsOf
Indicates that one party is against or rejects another party, proposal, or action specifically for the stated reasons or justification.
-
B.
opposedBy
Indicates that one entity actively resists, disagrees with, or works against the actions, views, or position of another entity.
-
C.
opposedLawType
Indicates that one law is opposed to, or in conflict with, another law of a specified type.
-
D.
canOppose
Indicates that one entity has the ability or capacity to resist, counteract, or act in opposition to another entity or its actions.
-
E.
opponentInCase
chosen
Indicates that two parties are on opposing sides in the same legal case or proceeding.
- 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_69ef5200fa0481908e28508d6e2c149e |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 27, 2026, 12:43 p.m.