Triple

T1805026
Position Surface form Disambiguated ID Type / Status
Subject Jaffna Tamil E40200 entity
Predicate hasAlternativeName P39 FINISHED
Object Yalpana Tamil E6357 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: Yalpana Tamil | Statement: [Jaffna Tamil, hasAlternativeName, Yalpana Tamil]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Yalpana Tamil
Context triple: [Jaffna Tamil, hasAlternativeName, Yalpana Tamil]
  • A. Lavani
    Lavani is a vibrant and rhythmic folk dance and musical style from Maharashtra, known for its powerful dholki beats, expressive storytelling, and often sensuous performances.
  • B. Santalī
    Santalī is an Austroasiatic language spoken primarily by the Santal people in eastern India, Bangladesh, Nepal, and Bhutan.
  • C. Tamil chosen
    Tamil is a classical Dravidian language spoken predominantly in the Indian state of Tamil Nadu and in parts of Sri Lanka, with a rich literary tradition spanning over two millennia.
  • D. Ponna
    Ponna was a prominent 10th-century Kannada poet of the Rashtrakuta court, renowned for his Jain devotional and classical literary works.
  • E. Baleswari Odia
    Baleswari Odia is a regional variety of the Odia language spoken primarily in the Balasore (Baleswar) region of Odisha, India.
  • 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_69a88643a3388190a612f2ebe1fb29e7 completed March 4, 2026, 7:21 p.m.
NER Named-entity recognition batch_69aa659648e8819085fafb60dc03f14b completed March 6, 2026, 5:26 a.m.
NED1 Entity disambiguation (via context triple) batch_69adb5df20948190943a60c209270b62 completed March 8, 2026, 5:46 p.m.
Created at: March 4, 2026, 7:32 p.m.