Triple
T24949356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Asian Canadians |
E624283
|
entity |
| Predicate | ethnicOriginCategoryInCensus |
P14216
|
FINISHED |
| Object | South Asian |
—
|
NE NERFINISHED |
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: South Asian | Statement: [South Asian Canadians, ethnicOriginCategoryInCensus, South Asian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ethnicOriginCategoryInCensus Context triple: [South Asian Canadians, ethnicOriginCategoryInCensus, South Asian]
-
A.
ethnicOrigin
Indicates the relationship where an entity is associated with a particular ethnic group or ancestry.
-
B.
ethnicCategoryIn
chosen
Indicates that an entity belongs to or is classified within a specified ethnic category in a given context.
-
C.
ethnicGroupClassifiedAs
Indicates that an ethnic group is categorized or designated as belonging to a particular classification or type of ethnic grouping.
-
D.
ethnicOrCulturalGroup
Indicates that one entity belongs to, is associated with, or is characterized by a particular ethnic or cultural group represented by the other entity.
-
E.
holderEthnicity
Indicates the ethnic background or group to which the holder of something (e.g., a document, account, or item) belongs.
- 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_69e2ff22e4c48190a0444b5a044f14e8 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d77f6e88190a4643ab2cbef567b |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 5:55 a.m.