Triple

T25777317
Position Surface form Disambiguated ID Type / Status
Subject Melanesian linguistic area E649186 entity
Predicate includesLanguageGroup P3349 FINISHED
Object Sepik languages
The Sepik languages are a diverse family of Papuan languages spoken primarily along the Sepik River region of northern Papua New Guinea.
E1151277 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: Sepik languages | Statement: [Melanesian linguistic area, includesLanguageGroup, Sepik 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: Sepik languages
Triple: [Melanesian linguistic area, includesLanguageGroup, Sepik languages]
Generated description
The Sepik languages are a diverse family of Papuan languages spoken primarily along the Sepik River region of northern Papua New Guinea.

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_69e7ab333b508190b6d708d8d9a328ed completed April 21, 2026, 4:52 p.m.
NER Named-entity recognition batch_69f5fe5d88548190b070af28fe052ad1 completed May 2, 2026, 1:38 p.m.
NED1 Entity disambiguation (via context triple) batch_6a11075c02c08190b3fb9d898df818cc completed May 23, 2026, 1:48 a.m.
NEDg Description generation batch_6a1107f68c64819090fff48a1bf286df completed May 23, 2026, 1:50 a.m.
NED2 Entity disambiguation (via description) batch_6a110834d2f881909a2c721b2b0ac4e8 completed May 23, 2026, 1:51 a.m.
Created at: April 22, 2026, 5:35 a.m.