Triple
T24791215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SJR |
E620254
|
entity |
| Predicate | primaryExchangeCountry |
P120946
|
FINISHED |
| Object | Canada |
E14901
|
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: Canada | Statement: [SJR, primaryExchangeCountry, Canada]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryExchangeCountry Context triple: [SJR, primaryExchangeCountry, Canada]
-
A.
primaryExchange
Indicates the main or most significant transfer or trade interaction occurring between two parties or systems.
-
B.
hasPrimaryExchangeCountryCode
chosen
Indicates the country code of the main securities exchange on which an entity is primarily listed or traded.
-
C.
primaryRouteCountry
Indicates the country that serves as the main or principal route location associated with the subject.
-
D.
primaryReferenceCountry
Indicates the main country that serves as the primary point of reference or association for the related entity.
-
E.
primaryExchangeFor
Indicates that one entity serves as the main or principal exchange platform or marketplace used for trading or transacting another entity.
- 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_69e2fabe77c8819085f7ce6486248139 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f62d89b89c8190afb372a8172111e7 |
completed | May 2, 2026, 4:59 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a1032e4d1c481909ea8bca17c0586c5 |
completed | May 22, 2026, 10:41 a.m. |
| PD | Predicate disambiguation | batch_69f62c1379f08190836c3e02b0c892df |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 18, 2026, 4:47 a.m.