Triple
T25804873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clay Township, Boone County, Indiana |
E649940
|
entity |
| Predicate | hasCensusYear |
P292
|
FINISHED |
| Object | 2010 |
—
|
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: 2010 | Statement: [Clay Township, Boone County, Indiana, hasCensusYear, 2010]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCensusYear Context triple: [Clay Township, Boone County, Indiana, hasCensusYear, 2010]
-
A.
basedOnCensusYear
Indicates that something (such as data, a decision, or a classification) is derived from or determined using information from a specific census year.
-
B.
hasCensusDay
Indicates the specific date on which a census is officially conducted or referenced for a given census event.
-
C.
populationCensusYear
chosen
Indicates the specific year in which an official population census was conducted or recorded for an entity.
-
D.
hasCensusFunction
Indicates that an entity holds an official role or responsibility related to conducting, managing, or supporting census activities.
-
E.
nextScheduledCensusYear
Indicates the year in which the next planned or officially scheduled census is to take place.
- 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_69e7ab35d264819095367f7e80c983ff |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f657f653448190a945b4751af8507d |
completed | May 2, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 22, 2026, 7:02 a.m.