Triple

T38541888
Position Surface form Disambiguated ID Type / Status
Subject JSE:SAB E924853 entity
Predicate hadUnderlyingCompanyOriginIn P66972 FINISHED
Object South Africa 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: South Africa | Statement: [JSE:SAB, hadUnderlyingCompanyOriginIn, South Africa]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hadUnderlyingCompanyOriginIn
Context triple: [JSE:SAB, hadUnderlyingCompanyOriginIn, South Africa]
  • A. underlyingCompany
    Indicates that one entity serves as the fundamental or base company upon which another entity (such as a product, instrument, or structure) is built, derived, or dependent.
  • B. underlyingCompanyFormedBy
    Indicates that an underlying company was created, established, or formed by a specified entity.
  • C. originatingCompany
    Indicates the company from which something (such as a product, document, transaction, or request) originally comes or is issued.
  • D. hasMajorCompanyOrigin
    Indicates that an entity originates from, was founded by, or initially developed within a major company.
  • E. hasUnderlyingCompanyOperationsIn chosen
    Indicates that a company’s core or foundational business activities take place within a specified geographic location or jurisdiction.
  • 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_69f76eadeac081909cdfdd0474cb6765 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fcdaa36f90819093f8661969990c7d completed May 7, 2026, 6:32 p.m.
PD Predicate disambiguation batch_69fcd8fefc588190b063d7ea1ec87b07 completed May 7, 2026, 6:25 p.m.
Created at: May 3, 2026, 4:32 p.m.