Triple

T18190360
Position Surface form Disambiguated ID Type / Status
Subject MS E435515 entity
Predicate associatedCompanyGlobalPresence P17483 FINISHED
Object operates in North America LITERAL 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: operates in North America | Statement: [MS, associatedCompanyGlobalPresence, operates in North America]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: associatedCompanyGlobalPresence
Context triple: [MS, associatedCompanyGlobalPresence, operates in North America]
  • A. associatedCompanyGlobalScope
    Indicates that there is a relationship linking an entity to a company at a global (worldwide) organizational scope.
  • B. hasCorporatePresence chosen
    Indicates that an organization maintains an official operational or business presence (such as offices, facilities, or legal registration) in a particular location or context.
  • C. associatedCompanyFoundedIn
    Indicates that the related company was founded in the specified year or time period.
  • D. relatedCompanyType
    Indicates the type or nature of the relationship that one company has to another company.
  • E. memberCompany
    Indicates that a company is formally part of, or affiliated as a member with, a larger organization, group, or association.
  • 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_69d8b90c7ec081909b4694ccecb449c6 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4e0016ec08190ae853dbc89865a41 completed April 19, 2026, 2 p.m.
PD Predicate disambiguation batch_69e4331e92408190ad607ba4956a3897 completed April 19, 2026, 1:42 a.m.
Created at: April 10, 2026, 10:31 a.m.