Triple
T262101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | China |
E5561
|
entity |
| Predicate | populationStatus |
P328
|
FINISHED |
| Object | over 1.4 billion inhabitants |
—
|
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 1.4 billion inhabitants | Statement: [China, populationStatus, over 1.4 billion inhabitants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: populationStatus Context triple: [China, populationStatus, over 1.4 billion inhabitants]
-
A.
population
chosen
Indicates the total number of individuals living in or present within a specified area or group.
-
B.
populationIncludes
Indicates that a population contains or encompasses the specified individual(s) or subgroup(s) as members or elements.
-
C.
populationClass
Indicates a categorical classification of a population based on shared characteristics, status, or demographic criteria.
-
D.
populationContext
Indicates the demographic or population-related setting or conditions within which an entity, event, or measurement is defined or interpreted.
-
E.
demographicScope
Indicates the specific population group or demographic segment to which something (e.g., a policy, study, product, or service) is targeted or applicable.
- 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_69a2580a64ac8190ad76e34bb0715b5e |
completed | Feb. 28, 2026, 2:50 a.m. |
| NER | Named-entity recognition | batch_69a25e2aba74819093eddd8d820260c0 |
completed | Feb. 28, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69a25b6c968c819094fc903a3a377e15 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:55 a.m.