Triple
T35853853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Census of Kentucky counties |
E1036441
|
entity |
| Predicate | previousCensusYear |
P172755
|
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: [U.S. Census of Kentucky counties, previousCensusYear, 2010]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousCensusYear Context triple: [U.S. Census of Kentucky counties, previousCensusYear, 2010]
-
A.
previousCensus
chosen
Indicates that one census event temporally precedes another in an ordered sequence of censuses.
-
B.
previousElectionYear
Indicates the year in which the immediately preceding election for the same office, position, or body took place.
-
C.
basedOnCensusYear
Indicates that something (such as data, a decision, or a classification) is derived from or determined using information from a specific census year.
-
D.
previousSingleYear
Indicates that one entity corresponds to the immediately preceding single year relative to another entity.
-
E.
populationCensusYear
Indicates the specific year in which an official population census was conducted or recorded for an 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_69f76e1b4aa481909630373171eb5ec6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff7bc112088190851501fb2a16103d |
completed | May 9, 2026, 6:24 p.m. |
| PD | Predicate disambiguation | batch_69ff7b45507c81909753866ad733601a |
completed | May 9, 2026, 6:21 p.m. |
Created at: May 3, 2026, 4:06 p.m.