Triple

T29498165
Position Surface form Disambiguated ID Type / Status
Subject Lang Son Province E748293 entity
Predicate hasRiver P165 FINISHED
Object Ky Cung River
The Ky Cung River is a significant river in northeastern Vietnam that flows through Lạng Sơn Province and plays an important role in the region’s ecology and local economy.
E1992859 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: Ky Cung River | Statement: [Lang Son Province, hasRiver, Ky Cung 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: Ky Cung River
Triple: [Lang Son Province, hasRiver, Ky Cung River]
Generated description
The Ky Cung River is a significant river in northeastern Vietnam that flows through Lạng Sơn Province and plays an important role in the region’s ecology and local economy.

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_69f0bd448c6881908aa6b475cefd5ddc completed April 28, 2026, 1:59 p.m.
NER Named-entity recognition batch_69f66c305c6c819092d8110baaee1ac7 completed May 2, 2026, 9:27 p.m.
NED1 Entity disambiguation (via context triple) batch_6a2f00fcf29c8190a0197b58109a7202 completed June 14, 2026, 7:29 p.m.
NEDg Description generation batch_6a2f01d797e48190bf1717ba725d7141 completed June 14, 2026, 7:32 p.m.
NED2 Entity disambiguation (via description) batch_6a2f02d3ff748190adb82f02b7629721 completed June 14, 2026, 7:36 p.m.
Created at: April 28, 2026, 4:20 p.m.