Triple
T10800338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asbestos Litigation Section |
E254820
|
entity |
| Predicate | usesProcedures |
P15181
|
FINISHED |
| Object | civil procedure rules of Illinois |
—
|
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: civil procedure rules of Illinois | Statement: [Asbestos Litigation Section, usesProcedures, civil procedure rules of Illinois]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesProcedures Context triple: [Asbestos Litigation Section, usesProcedures, civil procedure rules of Illinois]
-
A.
hasSpecialProcedure
chosen
Indicates that a particular entity is associated with or governed by a designated special procedure or process.
-
B.
hadProcedure
Indicates that a subject underwent or received a specific medical or clinical procedure.
-
C.
hasSurgery
Indicates that a surgical procedure is performed on or undergone by an entity.
-
D.
overseesProcedure
Indicates that one entity is responsible for supervising, managing, or directing the execution of a specific procedure performed by another entity.
-
E.
hasProceduralRole
Indicates that an entity participates in a process or procedure by fulfilling a specific functional role within that process.
- 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_69d6aa61c15c8190a1839550c56e75e1 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7336d1b5c8190949144bba2fa0e76 |
completed | April 9, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69d6f3188f00819094ee8d65b187a333 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:18 p.m.