Triple

T13895111
Position Surface form Disambiguated ID Type / Status
Subject Sambalpur Junction E334066 entity
Predicate connectsTo P845 FINISHED
Object Puri E476598 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: Puri | Statement: [Sambalpur Junction, connectsTo, Puri]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Puri
Context triple: [Sambalpur Junction, connectsTo, 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. 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.
  • C. Vikrampura
    Vikrampura was an important historical city that served as a principal royal center of the medieval Indian Pala dynasty in eastern India.
  • D. Mandapam
    Mandapam is a coastal town in Tamil Nadu, India, known as a gateway to Rameswaram and for its fishing and marine activities.
  • E. Dvaraka
    Dvaraka is an ancient and sacred coastal city in western India, revered in Hindu tradition as the legendary kingdom of Lord Krishna.
  • 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_69d81c5dd2d48190b7a5fc1e009de936 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de23a741908190bdf46d76c5f1411a completed April 14, 2026, 11:23 a.m.
NED1 Entity disambiguation (via context triple) batch_69f7c71eb1808190b0a3a28a8011e9c7 completed May 3, 2026, 10:07 p.m.
Created at: April 9, 2026, 10:15 p.m.