Triple
T14921320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metamora, Illinois |
E371514
|
entity |
| Predicate | historicCourthouseServedAs |
P88767
|
FINISHED |
| Object | county seat of Woodford County, 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: county seat of Woodford County, Illinois | Statement: [Metamora, Illinois, historicCourthouseServedAs, county seat of Woodford County, Illinois]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicCourthouseServedAs Context triple: [Metamora, Illinois, historicCourthouseServedAs, county seat of Woodford County, Illinois]
-
A.
courthouseHistoricUse
chosen
Indicates the historical function or role that a courthouse served in the past.
-
B.
hasCourthouse
Indicates that a location or jurisdiction possesses or contains a courthouse.
-
C.
courthouseLocatedIn
Indicates that a courthouse is situated within or at a specific geographic or administrative location.
-
D.
historicallyHoused
Indicates that one entity served as a location or container for another entity at some time in the past.
-
E.
usedAsCityHallFrom
Indicates that a building or location functioned as the official city hall of a municipality during a specified time period.
- 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_69d85cc7ea3481908228b5acb7d06f12 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded63121e48190b54eb2546acc3c93 |
completed | April 15, 2026, 12:05 a.m. |
| PD | Predicate disambiguation | batch_69de9a52ba988190a26e268b4ea083ea |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:34 a.m.