Triple
T2772025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Governor of Bangkok |
E61476
|
entity |
| Predicate | governsPopulationType |
P14168
|
FINISHED |
| Object | urban population |
—
|
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: urban population | Statement: [Governor of Bangkok, governsPopulationType, urban population]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governsPopulationType Context triple: [Governor of Bangkok, governsPopulationType, urban population]
-
A.
governedPopulation
chosen
Indicates that one entity serves as the governing authority over the population of another entity.
-
B.
hasPopulationType
Indicates that an entity’s population is classified according to a specific type or category (e.g., demographic, biological, or statistical grouping).
-
C.
hadPopulationType
Indicates that an entity possessed a particular classification or type of population during a given time or context.
-
D.
governsTerritoryType
Indicates that an authority or governing body exercises official control or administration over a specified type of territory.
-
E.
populationClass
Indicates a categorical classification of a population based on shared characteristics, status, or demographic criteria.
- 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_69ab4b7cd13481909174bca9809ed259 |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abddceb9d88190961e30d521a21552 |
completed | March 7, 2026, 8:11 a.m. |
| PD | Predicate disambiguation | batch_69abdcfed608819080988e93df7bdf7c |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:57 p.m.