Triple
T28084505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Illinois's 18th congressional district |
E709781
|
entity |
| Predicate | includedCounty |
P5971
|
FINISHED |
| Object | Peoria County, Illinois |
—
|
NE NERFINISHED |
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: Peoria County, Illinois | Statement: [Illinois's 18th congressional district, includedCounty, Peoria County, Illinois]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedCounty Context triple: [Illinois's 18th congressional district, includedCounty, Peoria County, Illinois]
-
A.
includesCounty
chosen
Indicates that a larger geographic or administrative region contains or encompasses a specific county within its boundaries.
-
B.
inCounty
Indicates that one entity is geographically or administratively located within the boundaries of a specified county.
-
C.
traditionalCountyIncludes
Indicates that a traditional or historic county geographically contains or encompasses another area or entity within its boundaries.
-
D.
sharesCountyWith
Indicates that two entities are located within the same county jurisdiction.
-
E.
associatedWithCounty
Indicates that an entity has a relationship or linkage to a specific county, such as jurisdiction, location, or administrative association.
- 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_69ef9b7037f0819095bb90eaccbcaf32 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69feafa1ba0081909013800b85a9f613 |
completed | May 9, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69feae58d62c81909d031f3df8992883 |
completed | May 9, 2026, 3:47 a.m. |
Created at: April 27, 2026, 8:54 p.m.