Triple
T36261364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Illinois probate judges |
E892094
|
entity |
| Predicate | courtDivision |
P47013
|
FINISHED |
| Object | probate division of circuit court |
—
|
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: probate division of circuit court | Statement: [Illinois probate judges, courtDivision, probate division of circuit court]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: courtDivision Context triple: [Illinois probate judges, courtDivision, probate division of circuit court]
-
A.
hasCourtDivision
chosen
Indicates that a court is organized into, or belongs to, a specific internal division or section within the judicial system.
-
B.
courtName
Indicates the official name assigned to a particular court within a legal or judicial system.
-
C.
courtCode
Indicates the specific court or judicial body associated with a legal case, proceeding, or record.
-
D.
judicialCircuit
Indicates the judicial circuit within which a legal entity, case, or jurisdiction is organized or falls under authority.
-
E.
courtCategory
Indicates the classification or type of court associated with a legal case, proceeding, or judicial body.
- 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_69f76e4699188190af045b11a840ce31 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7ba6d06f48190a71b5a2f19e2232f |
completed | May 3, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a4aad48190a62e41c5e39339d9 |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:09 p.m.