Triple

T7073153
Position Surface form Disambiguated ID Type / Status
Subject Pandya dynasty E164748 entity
Predicate port P1763 FINISHED
Object Korkai E639729 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: Korkai | Statement: [Pandya dynasty, port, Korkai]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Korkai
Context triple: [Pandya dynasty, port, Korkai]
  • A. Korkai chosen
    Korkai was an ancient port city in southern India that served as an early capital and major maritime trade center of the Pandya kingdom.
  • B. Keelakarai
    Keelakarai is a coastal town in Tamil Nadu, India, known for its historic mosques, maritime trading heritage, and culturally rich Muslim community.
  • C. Hogenakkal
    Hogenakkal is a small town in Tamil Nadu, India, known as the gateway to the famous Hogenakkal Falls on the Kaveri River.
  • D. Mahodayapuram
    Mahodayapuram was the principal royal city and political center of the medieval Chera kingdom in present-day Kerala, India.
  • E. 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.
  • 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_69c6887b96548190a8a9b3ac8adf4119 completed March 27, 2026, 1:39 p.m.
NER Named-entity recognition batch_69c6e4cb76548190bd98876f8ba925b7 completed March 27, 2026, 8:12 p.m.
NED1 Entity disambiguation (via context triple) batch_69c79c8ca5a48190bbfbf640fb1f778d completed March 28, 2026, 9:17 a.m.
Created at: March 27, 2026, 2:39 p.m.