Triple

T29084838
Position Surface form Disambiguated ID Type / Status
Subject Hailar E734077 entity
Predicate locatedOn P40 FINISHED
Object Hailar River
The Hailar River is a major river in northeastern China and eastern Mongolia that forms part of the upper reaches of the Argun River, contributing to the border between China and Russia.
 E1872811 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: Hailar River | Statement: [Hailar, locatedOn, Hailar 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: Hailar River
Triple: [Hailar, locatedOn, Hailar River]
Generated description
The Hailar River is a major river in northeastern China and eastern Mongolia that forms part of the upper reaches of the Argun River, contributing to the border between China and Russia.

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_69f05b0c0f28819086eae6e84f2ae472 completed April 28, 2026, 7 a.m.
NER Named-entity recognition batch_69f6614638d481909dd167f9c8c7055c completed May 2, 2026, 8:40 p.m.
NED1 Entity disambiguation (via context triple) batch_6a260bfbd67c8190944af3cc0eb77d6a completed June 8, 2026, 12:25 a.m.
NEDg Description generation batch_6a26103b50948190a67b288cf9f474ce completed June 8, 2026, 12:43 a.m.
NED2 Entity disambiguation (via description) batch_6a261bab40048190b31f5b12454bedbf completed June 8, 2026, 1:32 a.m.
Created at: April 28, 2026, 10:59 a.m.