Triple

T22308930
Position Surface form Disambiguated ID Type / Status
Subject Parshvanath Jain Temple E551460 entity
Predicate near P350 FINISHED
Object Junagadh city 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: Junagadh city | Statement: [Parshvanath Jain Temple, near, Junagadh city]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Junagadh city
Context triple: [Parshvanath Jain Temple, near, Junagadh city]
  • A. Junagadh chosen
    Junagadh is a historic city in western India known for its ancient fort, Buddhist caves, and proximity to the Girnar hills and Gir National Park.
  • B. Surendranagar
    Surendranagar is a city in the Indian state of Gujarat known historically as a regional trade and administrative center.
  • C. Veraval
    Veraval is a coastal city in the Indian state of Gujarat, known historically as a major fishing and port town near the pilgrimage center of Somnath.
  • D. Palanpur
    Palanpur is a prominent town in northern Gujarat, India, known historically as the former capital of the princely state of Palanpur and an important regional commercial center.
  • E. Bhuj
    Bhuj is a historic city in the Kutch district of Gujarat, India, known for its rich cultural heritage, traditional handicrafts, and role as a regional commercial and administrative center.
  • 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_69e11e46c0188190800181a4233f28fe completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f1574c8a248190bf5eef5be78381fd completed April 29, 2026, 12:56 a.m.
Created at: April 16, 2026, 8:42 p.m.