Triple

T23365042
Position Surface form Disambiguated ID Type / Status
Subject Sadras Dutch Fort E593292 entity
Predicate locatedIn P40 FINISHED
Object Sadras 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: Sadras | Statement: [Sadras Dutch Fort, locatedIn, Sadras]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sadras
Context triple: [Sadras Dutch Fort, locatedIn, Sadras]
  • A. Sadras chosen
    Sadras is a historic coastal town in Tamil Nadu, India, known for its Dutch-era fort and role as a former trading port on the Coromandel Coast.
  • B. Gundeshapur
    Gundeshapur was a prominent Sasanian city in southwestern Iran renowned as a major center of learning, medicine, and philosophy in late antiquity.
  • C. Taleqan
    Taleqan is a small mountainous city in northern Iran known for its cool climate, natural landscapes, and traditional rural architecture.
  • D. Tajrish
    Tajrish is a historic and bustling neighborhood in northern Tehran known for its traditional bazaar, central square, and proximity to the Alborz Mountains.
  • E. Esfarayen
    Esfarayen is a city in North Khorasan Province in northeastern Iran, known for its historical background and regional agricultural activities.
  • 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_69e25d2593c88190bcdf4a716a94ccb2 completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f1a0ab7fc481908b496ec9b543eddd completed April 29, 2026, 6:09 a.m.
Created at: April 17, 2026, 5:31 p.m.