Triple

T5876502
Position Surface form Disambiguated ID Type / Status
Subject C. V. Raman E130637 entity
Predicate hasSurname P18 FINISHED
Object Raman E130637 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: Raman | Statement: [C. V. Raman, hasSurname, Raman]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Raman
Context triple: [C. V. Raman, hasSurname, Raman]
  • A. Raman chosen
    Raman is a common Indian surname most famously associated with physicist C. V. Raman, a Nobel laureate known for discovering the Raman effect in light scattering.
  • B. Raj
    Raj is the given name of Raj Reddy, a pioneering computer scientist known for his foundational work in artificial intelligence and robotics.
  • C. Shankar
    Shankar is a prominent Indian film director best known for his big-budget, socially themed blockbuster movies in Tamil cinema.
  • D. Shankar
    Shankar is the surname of the renowned musical family that includes legendary sitar virtuoso Ravi Shankar and his daughter, singer-songwriter Norah Jones.
  • E. Ravi
    Ravi is a common Indian male given name of Sanskrit origin meaning "sun" or "sun god."
  • 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_69c0085523688190bfd487479ce819e6 completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c0362fb6948190bdbb3f1d446d070c completed March 22, 2026, 6:34 p.m.
NED1 Entity disambiguation (via context triple) batch_69c0b12242dc819093ccd41c9705dd72 completed March 23, 2026, 3:18 a.m.
Created at: March 22, 2026, 3:57 p.m.