Triple
T2323804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Law Division (Circuit Court of Cook County) |
E48239
|
entity |
| Predicate | typicalParties |
P7712
|
FINISHED |
| Object | individual plaintiffs |
—
|
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: individual plaintiffs | Statement: [Law Division (Circuit Court of Cook County), typicalParties, individual plaintiffs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalParties Context triple: [Law Division (Circuit Court of Cook County), typicalParties, individual plaintiffs]
-
A.
mainParties
Indicates the primary entities that are directly and centrally involved in a given relationship, event, or agreement.
-
B.
typicalParty
chosen
Indicates that an entity is a usual, standard, or characteristic participant in a given type of event, situation, or relationship.
-
C.
compactParties
Indicates that the referenced parties are participants in, or signatories to, the same compact or formal agreement.
-
D.
foundingParties
Indicates the entities that jointly establish or create an organization, institution, or agreement as its original founders.
-
E.
hasPartiesDescription
Indicates that a relationship or event includes a textual description of the parties involved.
- 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_69a88aa308a88190b0b86c011fda7fce |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc685f05481909c863b29d1f6bacd |
completed | March 7, 2026, 6:32 a.m. |
| PD | Predicate disambiguation | batch_69abc5909cc48190aab257313542dc49 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:49 p.m.