Triple

T10156206
Position Surface form Disambiguated ID Type / Status
Subject Sundar Pichai E233782 entity
Predicate givenName P17 FINISHED
Object Sundar E233782 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: Sundar | Statement: [Sundar Pichai, givenName, Sundar]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sundar
Context triple: [Sundar Pichai, givenName, Sundar]
  • A. Sundar chosen
    Sundar is the given name of Sundar Pichai, the Indian-American CEO of Alphabet Inc. and Google.
  • B. Sudarshan
    Sudarshan is a common Indian surname found across various regions and communities in India.
  • C. Sampati
    Sampati is a character in the Indian epic Ramayana, a vulture-king known for being Jatayu’s elder brother who aids Rama’s allies by revealing Sita’s whereabouts.
  • D. Arun
    Arun is a local government district and borough in West Sussex, England, named after the River Arun and encompassing coastal towns such as Bognor Regis and Littlehampton.
  • E. Kedar
    Kedar is traditionally regarded as one of the sons of Ishmael and the ancestor of a nomadic Arab tribe mentioned in biblical and historical sources.
  • 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_69ca848e80748190b91d1e04d35512c7 completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cdec3a5e7c819098b2f9ccbde7cf94 completed April 2, 2026, 4:10 a.m.
NED1 Entity disambiguation (via context triple) batch_69d2e65b9d4c8190b1f520ed08256372 completed April 5, 2026, 10:46 p.m.
Created at: March 30, 2026, 9:09 p.m.