Triple

T9926064
Position Surface form Disambiguated ID Type / Status
Subject Hasso Plattner E187923 entity
Predicate coFounded P104 FINISHED
Object SAP SE E35622 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: SAP SE | Statement: [Hasso Plattner, coFounded, SAP SE]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: SAP SE
Context triple: [Hasso Plattner, coFounded, SAP SE]
  • A. SAP
    SAP is the station code for Lisbon Santa Apolónia, one of the main railway terminals in Lisbon, Portugal.
  • B. SAP
    SAP is Sweden’s major center-left political party, historically associated with social democracy, the welfare state, and long periods of governing the country.
  • C. SAP
    SAP was the former official currency of South Africa, used before the adoption of the South African rand.
  • D. SAP chosen
    SAP is a leading global enterprise software company best known for its ERP solutions that help organizations manage business operations and customer relations.
  • E. SAP
    SAP is the commonly used abbreviation for the Société d’Anthropologie de Paris, a French learned society dedicated to the study of anthropology.
  • 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_69ca82b22a688190b52c75bd48429c10 completed March 30, 2026, 2:03 p.m.
NER Named-entity recognition batch_69cdb599e32c8190ac676fa89c131bb6 completed April 2, 2026, 12:17 a.m.
NED1 Entity disambiguation (via context triple) batch_69d20e143660819097a9fa96365bc25a completed April 5, 2026, 7:24 a.m.
Created at: March 30, 2026, 8:43 p.m.