Triple
T19363823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hereford and Worcester |
E484347
|
entity |
| Predicate | hadPopulationCensusYear |
P292
|
FINISHED |
| Object | 1991 |
—
|
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: 1991 | Statement: [Hereford and Worcester, hadPopulationCensusYear, 1991]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadPopulationCensusYear Context triple: [Hereford and Worcester, hadPopulationCensusYear, 1991]
-
A.
populationCensusYear
chosen
Indicates the specific year in which an official population census was conducted or recorded for an entity.
-
B.
hasPopulationAsOf
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.
hadPopulationFrom
Indicates that an entity had a specified population value during a particular time period starting from a given date.
-
E.
populationCensus2021
Indicates that a population count or demographic data is recorded as part of the 2021 census.
- 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_69d8e8d305088190ad13571532aa454c |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e619a9ac68819082cf9deadf526156 |
completed | April 20, 2026, 12:18 p.m. |
| PD | Predicate disambiguation | batch_69e4fd54f8e48190956e73dd8969164a |
completed | April 19, 2026, 4:05 p.m. |
Created at: April 10, 2026, 1:34 p.m.