Triple

T21110285
Position Surface form Disambiguated ID Type / Status
Subject Amrish Puri E520153 entity
Predicate familyName P18 FINISHED
Object Puri NE NERFINISHED

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: Puri | Statement: [Amrish Puri, familyName, Puri]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Puri
Context triple: [Amrish Puri, familyName, Puri]
  • A. Puri chosen
    Puri is a coastal city in the Indian state of Odisha, renowned as a major Hindu pilgrimage site and home to the famous Jagannath Temple.
  • B. Bhuvanesvari
    Bhuvanesvari is a Hindu goddess revered as a cosmic mother figure and a major form of the Divine Feminine in Shakta traditions.
  • C. Tamralipti
    Tamralipti was an ancient and prominent port city on the eastern coast of the Indian subcontinent that served as a key maritime hub for trade and cultural exchange between India and Southeast Asia.
  • D. Brahmpur
    Brahmpur is the fictional North Indian city that serves as the central setting of Vikram Seth’s novel "A Suitable Boy."
  • E. Vikrampura
    Vikrampura was an important historical city that served as a principal royal center of the medieval Indian Pala dynasty in eastern India.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0b509a318819092fbbcb21d1fe603 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e72101f7308190beb202a052ff04d2 completed April 21, 2026, 7:02 a.m.
Created at: April 16, 2026, 2:54 p.m.