Triple
T9269768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Abdullah Economic City |
E222794
|
entity |
| Predicate | plannedPopulation |
P87887
|
FINISHED |
| Object | over 2 million residents |
—
|
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 2 million residents | Statement: [King Abdullah Economic City, plannedPopulation, over 2 million residents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedPopulation Context triple: [King Abdullah Economic City, plannedPopulation, over 2 million residents]
-
A.
permanentPopulation
Indicates that an entity has a stable, long-term resident population rather than a temporary or transient presence.
-
B.
populationIncrease
Indicates that the number of individuals in a population has grown over a specified period of time.
-
C.
governedPopulation
Indicates that one entity serves as the governing authority over the population of another entity.
-
D.
populationScale
Indicates the relative size or magnitude of a population, typically categorizing it into broad scale levels (e.g., small, medium, large).
-
E.
hasPopulationApproximate
Indicates that an entity has an estimated or approximate population size, rather than an exact count.
- F. None of above. chosen
Provenance (4 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_69ca841ffe208190aa7bcffbef2f8379 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd078525308190abfb883123742d3f |
completed | April 1, 2026, 11:54 a.m. |
| PD | Predicate disambiguation | batch_69cc7a537bbc8190baee71f556e52a7b |
completed | April 1, 2026, 1:52 a.m. |
| PDg | Predicate description generation | batch_69cc95597be081908ece2491dd2f0f74 |
completed | April 1, 2026, 3:47 a.m. |
Created at: March 30, 2026, 7:33 p.m.