Triple
T33162781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vancouver South |
E848791
|
entity |
| Predicate | hasSignificantChineseCanadianCommunity |
P193495
|
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, hasSignificantChineseCanadianCommunity, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSignificantChineseCanadianCommunity Context triple: [Vancouver South, hasSignificantChineseCanadianCommunity, true]
-
A.
isOneOfLargestChinatownsIn
Indicates that a Chinatown is among the largest Chinatowns located within a specified geographic area or jurisdiction.
-
B.
ethnicCommunityContext
Indicates the cultural, social, or historical context related to an entity’s association with a particular ethnic community.
-
C.
permanentChinesePresence
Indicates a lasting, ongoing presence or involvement of Chinese entities in a particular place, context, or situation.
-
D.
majorChinatownIn
Indicates that a city or area contains a significant or primary Chinatown located within the specified place.
-
E.
ethnicCommunityBase
Indicates that an ethnic community is based in, originates from, or is primarily associated with a particular place or area.
- 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_69f3495b02d08190bb3d366823dffc21 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd485f57dc8190820365396d041991 |
completed | May 8, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69fd47d35da081908bec8901018d186c |
completed | May 8, 2026, 2:17 a.m. |
| PDg | Predicate description generation | batch_69fd485e0c20819099756b4fe39ac326 |
completed | May 8, 2026, 2:20 a.m. |
Created at: May 1, 2026, 1:28 a.m.