Triple
T378430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Circuit Court of Cook County |
E8620
|
entity |
| Predicate | isLargestBy |
P4495
|
FINISHED |
| Object | number of judges in 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: number of judges in Illinois | Statement: [Circuit Court of Cook County, isLargestBy, number of judges in Illinois]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLargestBy Context triple: [Circuit Court of Cook County, isLargestBy, number of judges in Illinois]
-
A.
isLargestOf
chosen
Indicates that one entity has the greatest size, extent, or magnitude among a specified set of entities.
-
B.
isMaximumWhen
Indicates that a quantity or function reaches its greatest possible value under specified conditions or at a particular point.
-
C.
isOldest
Indicates that one entity has a greater age than all other relevant entities in the comparison set.
-
D.
isLargestCityIn
Indicates that one city has the greatest population or size compared to all other cities within a specified region or administrative area.
-
E.
isOldestOrderOf
Indicates that one order is the earliest or first created among a set of related orders for a given context or entity.
- 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_69a2e7f47dd08190a4e294ccbbe46cd4 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec2974988190a1d6316cbb5159c8 |
completed | Feb. 28, 2026, 1:22 p.m. |
| PD | Predicate disambiguation | batch_69a2e96351cc8190a55adf95f8c27e9e |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.