Triple
T1411421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sanlam |
E31812
|
entity |
| Predicate | hasSubsidiary |
P254
|
FINISHED |
| Object | Sanlam Corporate |
E31812
|
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: Sanlam Corporate | Statement: [Sanlam, hasSubsidiary, Sanlam Corporate]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sanlam Corporate Context triple: [Sanlam, hasSubsidiary, Sanlam Corporate]
-
A.
Sanlam
chosen
Sanlam is a major South African financial services group offering insurance, investment, and wealth management solutions across multiple markets.
-
B.
JSE Limited
JSE Limited is the Johannesburg-based stock exchange and the primary securities market for South Africa and much of the African continent.
-
C.
Swiss Re
Swiss Re is a leading global reinsurance company headquartered in Zurich, Switzerland, providing risk transfer and insurance solutions worldwide.
-
D.
Protective Life Corporation
Protective Life Corporation is a U.S.-based insurance and financial services company known for offering life insurance, annuities, and asset protection products.
-
E.
Suncorp Group
Suncorp Group is a major Australian finance, insurance, and banking corporation headquartered in Brisbane.
- 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_69a49919a994819086528951bc224775 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c3e1da988190bc7c187e193539b6 |
completed | March 1, 2026, 10:55 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad0e67dbf88190a2a15baca5b9e79d |
completed | March 8, 2026, 5:51 a.m. |
Created at: March 1, 2026, 7:59 p.m.