Triple

T36660591
Position Surface form Disambiguated ID Type / Status
Subject Mario Schlosser E905110 entity
Predicate formerChiefExecutiveOf P6143 FINISHED
Object Oscar Health 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: Oscar Health | Statement: [Mario Schlosser, formerChiefExecutiveOf, Oscar Health]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: formerChiefExecutiveOf
Context triple: [Mario Schlosser, formerChiefExecutiveOf, Oscar Health]
  • A. formerCEO chosen
    Indicates that one entity previously held, but no longer holds, the position of chief executive officer of the other entity.
  • B. hasFormerChiefExecutive
    Indicates that an entity previously held the role of chief executive for another entity.
  • C. coChiefExecutiveOfficerOf
    Indicates that a person jointly holds the top executive leadership position of a company or organization, sharing chief executive officer responsibilities with one or more others.
  • D. formerDirector
    Indicates that one entity previously held the position of director of the other entity but no longer does.
  • E. formerNonExecutiveChairman
    Indicates that one entity previously held, but no longer holds, the role of non-executive chairman of another entity.
  • 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_69f76e6e3b908190970251b30f76ad71 completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_6a00ab25c5b48190ad07ff508392ef56 completed May 10, 2026, 3:58 p.m.
PD Predicate disambiguation batch_6a00a8a5cfc48190bbe97fb2bbd1b947 completed May 10, 2026, 3:47 p.m.
Created at: May 3, 2026, 4:11 p.m.