Triple
T21079190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kendall County Circuit Court |
E519314
|
entity |
| Predicate | caseOrigin |
P81213
|
FINISHED |
| Object | cases arising in Kendall County |
—
|
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: cases arising in Kendall County | Statement: [Kendall County Circuit Court, caseOrigin, cases arising in Kendall County]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: caseOrigin Context triple: [Kendall County Circuit Court, caseOrigin, cases arising in Kendall County]
-
A.
caseNumber
Indicates the unique identifying number assigned to a particular legal or administrative case.
-
B.
caseTypes
chosen
Indicates the types or categories of cases associated with or applicable to an entity or situation.
-
C.
primaryCase
Indicates that an entity is the main or leading instance in a set of related cases or occurrences.
-
D.
caseLoad
Indicates the number or collection of cases, tasks, or matters currently assigned to or handled by an entity.
-
E.
originatingJurisdiction
Indicates the jurisdiction (such as a country, state, or legal authority) from which something originally comes or under whose laws it was first established.
- 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_69e0b506e59c8190849b71ed07929215 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e702d939e08190a37d7b7cc1872ad5 |
completed | April 21, 2026, 4:53 a.m. |
| PD | Predicate disambiguation | batch_69e5dbfcd5e881908f1e4e0d2d237856 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:49 p.m.