Triple
T12600201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lisle Township Clerk |
E300836
|
entity |
| Predicate | isResponsibleFor |
P636
|
FINISHED |
| Object | maintaining township contracts and agreements |
—
|
LITERAL FINISHED |
How this triple was built (1 step)
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: maintaining township contracts and agreements | Statement: [Lisle Township Clerk, isResponsibleFor, maintaining township contracts and agreements]
Provenance (2 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_69d7bdea2ca881908f379526c13b1145 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d954d096d08190afa1f685bad68d35 |
completed | April 10, 2026, 7:51 p.m. |
Created at: April 9, 2026, 5:09 p.m.