Triple

T7755501
Position Surface form Disambiguated ID Type / Status
Subject Roach E175885 entity
Predicate hasVariant P455 FINISHED
Object Roche E533363 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: Roche | Statement: [Roach, hasVariant, Roche]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Roche
Context triple: [Roach, hasVariant, Roche]
  • A. Roche chosen
    Roche is a common surname of French origin borne by various notable individuals across fields such as architecture, politics, and the arts.
  • B. Roche
    Roche is a major Swiss multinational healthcare company and one of the world’s leading pharmaceutical and diagnostics firms.
  • C. Novartis
    Novartis is a global Swiss-based pharmaceutical company known for developing innovative medicines across a wide range of therapeutic areas.
  • D. Sandoz
    Sandoz is a historic Swiss pharmaceutical company best known as a predecessor of Novartis and a major player in generic medicines.
  • E. Sanofi
    Sanofi is a major French multinational pharmaceutical company known for developing prescription medicines, vaccines, and consumer healthcare products worldwide.
  • 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_69c6996180088190832e38e8d83ff54a completed March 27, 2026, 2:51 p.m.
NER Named-entity recognition batch_69c703d9d8fc8190b51faeb081ee425f completed March 27, 2026, 10:25 p.m.
NED1 Entity disambiguation (via context triple) batch_69c8be5dbf5881908d07d70c8ae061a5 completed March 29, 2026, 5:53 a.m.
Created at: March 27, 2026, 4:08 p.m.