Triple
T6974214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sanlam Limited |
E161674
|
entity |
| Predicate | tradedAs |
P2822
|
FINISHED |
| Object | JSE:SLM |
E161674
|
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: JSE:SLM | Statement: [Sanlam Limited, tradedAs, JSE:SLM]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: JSE:SLM Context triple: [Sanlam Limited, tradedAs, JSE:SLM]
-
A.
SL4
SL4 is a branch of Boston’s MBTA Silver Line bus rapid transit service that runs between downtown and the Seaport/South Station area.
-
B.
SL2
SL2 is a branch of Boston’s MBTA Silver Line bus rapid transit service that connects South Station with the Seaport and Design Center area.
-
C.
SJM
SJM is the National Rail station code for St. James railway station in Liverpool, England.
-
D.
SLM
chosen
SLM is the stock ticker symbol for Sanlam, a major South African financial services group offering insurance, investment, and wealth management products.
-
E.
JES2
JES2 (Job Entry Subsystem 2) is an IBM mainframe component that manages the input, scheduling, and output of batch jobs and print workloads in the z/OS operating system.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69c68854a0d88190bc0bf82263f1afce |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6db3bda908190a10a91dc8d043ef1 |
completed | March 27, 2026, 7:32 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c761a6bbdc81908c96871f151db279 |
completed | March 28, 2026, 5:05 a.m. |
Created at: March 27, 2026, 2:30 p.m.