Triple
T24949328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Asian Canadians |
E624283
|
entity |
| Predicate | languageCommunityIncludes |
P5562
|
FINISHED |
| Object | Punjabi speakers |
—
|
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: Punjabi speakers | Statement: [South Asian Canadians, languageCommunityIncludes, Punjabi speakers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageCommunityIncludes Context triple: [South Asian Canadians, languageCommunityIncludes, Punjabi speakers]
-
A.
hasLanguageCommunity
chosen
Indicates that an entity is associated with or serves a particular language community.
-
B.
languageLocalCommunities
Indicates that a language is used, maintained, or holds significance within specific local communities or regions.
-
C.
languageUsedInLocality
Indicates that a particular language is used or spoken within a specific locality or geographic area.
-
D.
languageGroupSpoken
Indicates that a particular language group is spoken or used for communication by an entity.
-
E.
languageOfSurroundingCulture
Indicates that one entity is the language predominantly used or characteristic of the surrounding culture associated with another entity.
- 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_69f661b58ac48190907b6c6e9ccc2c59 |
completed | May 2, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 18, 2026, 5:55 a.m.