Triple

T16592466
Position Surface form Disambiguated ID Type / Status
Subject Nicola River E403123 entity
Predicate hasTributary P415 FINISHED
Object Clapperton Creek
Clapperton Creek is a small tributary stream in British Columbia, Canada, that feeds into the Nicola River within the province’s interior plateau region.
E1639105 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: Clapperton Creek | Statement: [Nicola River, hasTributary, Clapperton Creek]
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: Clapperton Creek
Triple: [Nicola River, hasTributary, Clapperton Creek]
Generated description
Clapperton Creek is a small tributary stream in British Columbia, Canada, that feeds into the Nicola River within the province’s interior plateau region.

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_69d88387363c8190a97a0c942130de97 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e359a123e8819095cd73cd848a3345 completed April 18, 2026, 10:14 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0fee3b637c8190ae6f8ba04690247d completed May 22, 2026, 5:48 a.m.
NEDg Description generation batch_6a0ff0c57b088190b031ea186a987e32 completed May 22, 2026, 5:59 a.m.
NED2 Entity disambiguation (via description) batch_6a0ff16636008190a4267f6b8d8e3bb2 completed May 22, 2026, 6:02 a.m.
Created at: April 10, 2026, 5:16 a.m.