Triple
T3984198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bluewell, West Virginia |
E86830
|
entity |
| Predicate | hasPopulationCensus2010 |
P5555
|
FINISHED |
| Object | 2192 |
—
|
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: 2192 | Statement: [Bluewell, West Virginia, hasPopulationCensus2010, 2192]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPopulationCensus2010 Context triple: [Bluewell, West Virginia, hasPopulationCensus2010, 2192]
-
A.
rankInUS2010Census
Indicates the numerical position of an entity in the ranking of occurrences within the 2010 United States Census.
-
B.
hasPopulationAsOf
chosen
Indicates that a population count is associated with a specific point or date in time when that population figure was valid or recorded.
-
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.
populationCensus2021
Indicates that a population count or demographic data is recorded as part of the 2021 census.
-
E.
census
Indicates that an official count or survey is conducted to determine the number and characteristics of a population within a defined area or group.
- 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_69aed93fd9d4819085d3b2137d2346cb |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefa3ef7ac8190abe02f440ff83c43 |
completed | March 9, 2026, 4:50 p.m. |
| PD | Predicate disambiguation | batch_69aef8f492ac819089dbb9436dbcdd2b |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:33 p.m.