Triple

T13976968
Position Surface form Disambiguated ID Type / Status
Subject Kural literature E336210 entity
Predicate relatedConcept P37 FINISHED
Object Porul E202416 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: Porul | Statement: [Kural literature, relatedConcept, Porul]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Porul
Context triple: [Kural literature, relatedConcept, Porul]
  • A. Porul chosen
    Porul is the second section of the ancient Tamil classic Tirukkural, focusing on ethics, governance, politics, and social conduct.
  • B. Paravaqar
    Paravaqar is a small town located in Armenia's northeastern Tavush Province, known for its rural setting and proximity to forested, mountainous landscapes.
  • C. Piro
    Piro is an alternate name for the Yine language, an indigenous Arawakan language spoken in Peru.
  • D. Piro
    Piro is a town in the Bhojpur district of Bihar, India, known as one of the district’s principal urban and commercial centers.
  • E. Parea
    Parea is a small coastal village on the island of Huahine in French Polynesia, known for its tranquil beaches and traditional Polynesian atmosphere.
  • 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_69d81c639e808190a0e4b4f3d31c6a59 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de2e90dc148190b38e339aac0de484 completed April 14, 2026, 12:09 p.m.
NED1 Entity disambiguation (via context triple) batch_69fba1e1eb108190b3c0739b94556172 completed May 6, 2026, 8:17 p.m.
Created at: April 9, 2026, 10:18 p.m.