Triple

T35222221
Position Surface form Disambiguated ID Type / Status
Subject Tinglayan E1016988 entity
Predicate hasLanguage P15 FINISHED
Object Kalinga languages
The Kalinga languages are a group of closely related Austronesian languages spoken by the Kalinga people in the Cordillera region of northern Luzon in the Philippines.
E145495 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: Kalinga languages | Statement: [Tinglayan, hasLanguage, Kalinga languages]
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: Kalinga languages
Triple: [Tinglayan, hasLanguage, Kalinga languages]
Generated description
The Kalinga languages are a group of closely related Austronesian languages spoken by the Kalinga people in the Cordillera region of northern Luzon in the Philippines.

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_69f76de072908190ab65038a8a7b6a79 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69f78ea3f3c48190bdbbeb4db8da0302 completed May 3, 2026, 6:06 p.m.
NED1 Entity disambiguation (via context triple) batch_6a380f9f82888190a38d6cc63056f082 completed June 21, 2026, 4:21 p.m.
NEDg Description generation batch_6a38138dec888190858023eda98865b4 completed June 21, 2026, 4:38 p.m.
NED2 Entity disambiguation (via description) batch_6a3813e438d4819094ba23728ef9bae1 completed June 21, 2026, 4:40 p.m.
Created at: May 3, 2026, 4:02 p.m.