Triple

T10899941
Position Surface form Disambiguated ID Type / Status
Subject Claus Wellenreuther E257410 entity
Predicate coFounded P104 FINISHED
Object SAP 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 | Statement: [Claus Wellenreuther, coFounded, SAP]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: SAP
Context triple: [Claus Wellenreuther, coFounded, SAP]
  • A. 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.
  • B. 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.
  • C. SAP
    SAP is the station code for Lisbon Santa Apolónia, one of the main railway terminals in Lisbon, Portugal.
  • D. 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.
  • E. SAP
    SAP was the former official currency of South Africa, used before the adoption of the South African rand.
  • 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_69d6aa8550c8819095508a2ed9acf3db completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d761a2f02881908b70be6499dd8d98 completed April 9, 2026, 8:21 a.m.
NED1 Entity disambiguation (via context triple) batch_69e216c69b088190b8fa192cd8fe23ed completed April 17, 2026, 11:17 a.m.
Created at: April 8, 2026, 9:21 p.m.