Triple
T33162779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vancouver South |
E848791
|
entity |
| Predicate | hasHighImmigrantPopulation |
P4812
|
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: [Vancouver South, hasHighImmigrantPopulation, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHighImmigrantPopulation Context triple: [Vancouver South, hasHighImmigrantPopulation, true]
-
A.
hasImmigrantCommunitiesFrom
Indicates that a place or region contains established communities of people who have immigrated from a specified origin location.
-
B.
immigrantPopulationShare
chosen
Indicates the proportion of a total population that is made up of immigrants.
-
C.
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.
-
D.
hasRefugeePopulation
Indicates that an entity hosts, contains, or is associated with a population of refugees.
-
E.
immigratedTo
Indicates that an entity moved from its country of origin to live permanently in another specified country or region.
- 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_69f3495b02d08190bb3d366823dffc21 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fec00f27988190955de6b6348a4d97 |
completed | May 9, 2026, 5:03 a.m. |
| PD | Predicate disambiguation | batch_69febd52037c8190b475dbd50fdbc13e |
completed | May 9, 2026, 4:51 a.m. |
Created at: May 1, 2026, 1:28 a.m.