Triple
T22000418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burnaby South |
E543308
|
entity |
| Predicate | hasSignificantImmigrantPopulation |
P1898
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Burnaby South, hasSignificantImmigrantPopulation, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSignificantImmigrantPopulation Context triple: [Burnaby South, hasSignificantImmigrantPopulation, true]
-
A.
hasImmigrantCommunitiesFrom
Indicates that a place or region contains established communities of people who have immigrated from a specified origin location.
-
B.
hasSignificantEmigrationTo
Indicates that a substantial number of people leave one place, group, or entity to move and settle in another specific place, group, or entity.
-
C.
immigrantPopulationShare
Indicates the proportion of a total population that is made up of immigrants.
-
D.
hasSignificantPopulationGroup
chosen
Indicates that an entity contains or is associated with a notable or substantial subgroup of a population, distinguished by shared characteristics or attributes.
-
E.
hasRefugeePopulation
Indicates that an entity hosts, contains, or is associated with a population of refugees.
- 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_69e11e2c814c8190837d072789000486 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f127699a7881908a80b6e9e33fcc0b |
completed | April 28, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69e6f62dc9d88190ae387f145f9528de |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:20 p.m.