Triple
T31884502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Windscale fire |
E813969
|
entity |
| Predicate | exposedPopulationEstimate |
P3412
|
FINISHED |
| Object | hundreds of thousands of people |
—
|
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: hundreds of thousands of people | Statement: [Windscale fire, exposedPopulationEstimate, hundreds of thousands of people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exposedPopulationEstimate Context triple: [Windscale fire, exposedPopulationEstimate, hundreds of thousands of people]
-
A.
hasPopulationApproximate
chosen
Indicates that an entity has an estimated or approximate population size, rather than an exact count.
-
B.
envisionedPopulation
Indicates a relationship where an entity specifies or projects an expected or target population size for something (such as a place, project, or scenario).
-
C.
peakPopulationApproximate
Indicates that the peak population of an entity is known only approximately rather than as an exact value.
-
D.
plannedPopulation
Indicates the intended or projected number of individuals expected to occupy or use something, such as a facility, area, or system, according to a plan.
-
E.
lastKnownPopulations
Indicates the most recently recorded population counts associated with an entity or set of entities.
- 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_69f348ed74bc81909846aaa6a3c7318c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b0daa4988190b78498e7da6a30dd |
completed | May 3, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69f6aca59d4881908d14ed47962703bd |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 11:57 p.m.