Triple
T16522315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gargrave |
E401348
|
entity |
| Predicate | population_census2011 |
P292
|
FINISHED |
| Object | approximately 1800 |
—
|
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: approximately 1800 | Statement: [Gargrave, population_census2011, approximately 1800]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: population_census2011 Context triple: [Gargrave, population_census2011, approximately 1800]
-
A.
populationCensus2021
Indicates that a population count or demographic data is recorded as part of the 2021 census.
-
B.
populationCensusAuthority
Indicates that an entity serves as the official authority responsible for conducting and overseeing population censuses for a given jurisdiction.
-
C.
populationCensus2016
Indicates that the relationship or data pertains to population figures as recorded in the 2016 census.
-
D.
populationCensusYear
chosen
Indicates the specific year in which an official population census was conducted or recorded for an entity.
-
E.
populationBasis
Indicates that a population measurement is based on, derived from, or defined with respect to a particular reference, criterion, or underlying basis.
- 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_69d883838abc8190bc79cb2d41733ce2 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e8158cc8190aa77c6d37bd7ec76 |
completed | April 18, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69e296995d388190b88ebe189dce890d |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:14 a.m.