Triple
T349901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glasgow |
E7418
|
entity |
| Predicate | hasApproximatePopulation |
P3412
|
FINISHED |
| Object | over 600000 |
—
|
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: over 600000 | Statement: [Glasgow, hasApproximatePopulation, over 600000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximatePopulation Context triple: [Glasgow, hasApproximatePopulation, over 600000]
-
A.
hasPopulationApproximate
chosen
Indicates that an entity has an estimated or approximate population size, rather than an exact count.
-
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.
metropolitanAreaPopulationApproximate
Indicates that the predicate specifies an approximate total population size for a given metropolitan area.
-
D.
hasPopulationStatus
Indicates the current demographic condition or classification of a population associated with an entity.
-
E.
hasPopulationType
Indicates that an entity’s population is classified according to a specific type or category (e.g., demographic, biological, or statistical grouping).
- 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_69a2e7e696948190bebc966535995e45 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2eb1f028c819098fa6480b4ca5cf0 |
completed | Feb. 28, 2026, 1:18 p.m. |
| PD | Predicate disambiguation | batch_69a2e955d1f88190bd687c46fa7c5469 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.