Triple
T38541479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TSX:TPX.B |
E924843
|
entity |
| Predicate | associatedCompanyOperationsRegion |
P6665
|
FINISHED |
| Object | North America |
E335
|
NE 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: North America | Statement: [TSX:TPX.B, associatedCompanyOperationsRegion, North America]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedCompanyOperationsRegion Context triple: [TSX:TPX.B, associatedCompanyOperationsRegion, North America]
-
A.
associatedCompanyGlobalScope
Indicates that there is a relationship linking an entity to a company at a global (worldwide) organizational scope.
-
B.
operatedInRegion
chosen
Indicates that an entity conducted operations or activities within a specified geographic region.
-
C.
operatedByRegion
Indicates that an entity is managed, controlled, or administered by a specific geographic region or regional authority.
-
D.
hasHeadquartersInRegion
Indicates that an organization’s main administrative or corporate headquarters is located within a specified geographic region.
-
E.
operatesToRegion
Indicates that an agent conducts operations or provides services directed toward or within a specified region.
- F. None of above.
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_69f76eadeac081909cdfdd0474cb6765 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41ea882a0c81909e716d07dc576e78 |
completed | June 29, 2026, 3:46 a.m. |
| PD | Predicate disambiguation | batch_6a037a1e32108190897356d6a7fed879 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:32 p.m.