Triple

T23496610
Position Surface form Disambiguated ID Type / Status
Subject Kolathunadu E571720 entity
Predicate knownAs P39 FINISHED
Object Chirakkal kingdom
Chirakkal kingdom was a historic feudal kingdom in northern Kerala, India, ruled by the Kolathiri royal family and known for its role in the region’s political and maritime history.
E1592546 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: Chirakkal kingdom | Statement: [Kolathunadu, knownAs, Chirakkal kingdom]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Chirakkal kingdom
Triple: [Kolathunadu, knownAs, Chirakkal kingdom]
Generated description
Chirakkal kingdom was a historic feudal kingdom in northern Kerala, India, ruled by the Kolathiri royal family and known for its role in the region’s political and maritime history.

Provenance (5 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_69e245b4829881909b77a70e942bbd54 completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f1a7e00384819092729319a378d4ab completed April 29, 2026, 6:40 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0f454fcba88190a622f99374816478 completed May 21, 2026, 5:47 p.m.
NEDg Description generation batch_6a0f46b69d288190b3fb6dcea9fb44b5 completed May 21, 2026, 5:53 p.m.
NED2 Entity disambiguation (via description) batch_6a0f476e8eb88190a895453552c92b9a completed May 21, 2026, 5:57 p.m.
Created at: April 17, 2026, 6:05 p.m.