Triple

T20840161
Position Surface form Disambiguated ID Type / Status
Subject Kofarnihon River E513072 entity
Predicate hasTributary P415 FINISHED
Object Elok River
The Elok River is a tributary watercourse that feeds into the Kofarnihon River within the river systems of Central Asia.
E1890446 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: Elok River | Statement: [Kofarnihon River, hasTributary, Elok River]
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: Elok River
Triple: [Kofarnihon River, hasTributary, Elok River]
Generated description
The Elok River is a tributary watercourse that feeds into the Kofarnihon River within the river systems of Central Asia.

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_69e0b4cf62a88190bbf92351e9e57259 completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6c34a60848190b33078172675f8d7 completed April 21, 2026, 12:22 a.m.
NED1 Entity disambiguation (via context triple) batch_6a26f19ad7c48190b01dfaea5f71b7bd completed June 8, 2026, 4:45 p.m.
NEDg Description generation batch_6a26f66b547081909ac88e14bf340493 completed June 8, 2026, 5:05 p.m.
NED2 Entity disambiguation (via description) batch_6a26f7d1e25481909fbe21144c0c22b6 completed June 8, 2026, 5:11 p.m.
Created at: April 16, 2026, 12:43 p.m.