Triple
T31931978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ursy |
E815276
|
entity |
| Predicate | populationMeasurementYear |
P5555
|
FINISHED |
| Object | around 2020 |
—
|
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: around 2020 | Statement: [Ursy, populationMeasurementYear, around 2020]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: populationMeasurementYear Context triple: [Ursy, populationMeasurementYear, around 2020]
-
A.
populationCensusYear
Indicates the specific year in which an official population census was conducted or recorded for an entity.
-
B.
populationMeasurementBy
Indicates that a population quantity or statistic is determined, recorded, or reported by a specified agent, method, or source.
-
C.
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.
-
D.
populationCountedIn
Indicates that the population of one entity is measured, recorded, or included within the population statistics of another entity.
-
E.
populationDemonym
Indicates the term used to refer to the people or inhabitants associated with a particular place or region.
- 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_69f348f3035c81908558e2339955abb3 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 1, 2026, 12:04 a.m.