Triple
T13487641
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cité Industrielle |
E318547
|
entity |
| Predicate | hasPlannedPopulation |
P87887
|
FINISHED |
| Object | 35000 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: 35000 inhabitants | Statement: [Cité Industrielle, hasPlannedPopulation, 35000 inhabitants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlannedPopulation Context triple: [Cité Industrielle, hasPlannedPopulation, 35000 inhabitants]
-
A.
plannedPopulation
chosen
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.
-
B.
hasPopulationStatus
Indicates the current demographic condition or classification of a population associated with an entity.
-
C.
hasDependentPopulation
Indicates that an entity has a population of individuals who are economically or socially dependent on others for support.
-
D.
hasPopulationApproximate
Indicates that an entity has an estimated or approximate population size, rather than an exact count.
-
E.
hasPopulationScale
Indicates the relative size or magnitude of a population associated with an entity, typically expressed as a qualitative or categorical scale.
- 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_69d806b6bfec819089222715b2e86c8e |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf3b9b488190bb4e11424ff599c8 |
completed | April 12, 2026, 2:42 p.m. |
| PD | Predicate disambiguation | batch_69dbae06061881909a6a6032e0507587 |
completed | April 12, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:42 p.m.