Triple

T4121795
Position Surface form Disambiguated ID Type / Status
Subject Dutch Coromandel E92628 entity
Predicate hadSettlement P16159 FINISHED
Object Sadras E127898 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: Sadras | Statement: [Dutch Coromandel, hadSettlement, Sadras]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sadras
Context triple: [Dutch Coromandel, hadSettlement, 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. Sarab
    Sarab is a city in northwestern Iran known for its location in East Azerbaijan Province and its surrounding volcanic mineral springs.
  • D. Hormuzd
    Hormuzd is a masculine given name most notably borne by Hormuzd Rassam, a 19th-century Assyriologist and archaeologist known for his discoveries of ancient Mesopotamian artifacts.
  • E. Yasna
    Yasna is a central Zoroastrian liturgical ceremony and its associated collection of sacred texts, forming one of the core sections of the Avesta.
  • 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_69aed9685f70819086932777aec8d959 completed March 9, 2026, 2:30 p.m.
NER Named-entity recognition batch_69af0b2c76fc8190b3cd9facfcd6e427 completed March 9, 2026, 6:02 p.m.
NED1 Entity disambiguation (via context triple) batch_69b576b13cc881908fea25c686141546 completed March 14, 2026, 2:54 p.m.
Created at: March 9, 2026, 3:41 p.m.