Triple
T24949369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Asian Canadians |
E624283
|
entity |
| Predicate | earlySettlementRegion |
P102334
|
FINISHED |
| Object | British Columbia |
—
|
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: British Columbia | Statement: [South Asian Canadians, earlySettlementRegion, British Columbia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earlySettlementRegion Context triple: [South Asian Canadians, earlySettlementRegion, British Columbia]
-
A.
settledRegion
Indicates that an entity has established a lasting presence or habitation within a particular geographic region.
-
B.
regionOfEarlyExpansion
chosen
Indicates that a location served as an initial area where an entity, influence, or phenomenon began to grow or spread outward.
-
C.
originalSettlement
Indicates that one entity is the initial or first-established settlement location associated with another entity.
-
D.
originOfSettlement
Indicates the place, source, or starting point from which a settlement was established or originated.
-
E.
modernSettlementArea
Indicates the geographic area occupied by a settlement in its modern or current form.
- 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.