Triple

T33587276
Position Surface form Disambiguated ID Type / Status
Subject Romainmôtier-Envy E860317 entity
Predicate locatedOn P40 FINISHED
Object Nozon River
The Nozon River is a small watercourse in the canton of Vaud in western Switzerland, known for flowing through rural valleys and historic villages before joining the Orbe River.
E2297594 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: Nozon River | Statement: [Romainmôtier-Envy, locatedOn, Nozon 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: Nozon River
Triple: [Romainmôtier-Envy, locatedOn, Nozon River]
Generated description
The Nozon River is a small watercourse in the canton of Vaud in western Switzerland, known for flowing through rural valleys and historic villages before joining the Orbe River.

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_69f3497e70e48190951c94d072879bec completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69f6f774f2f88190b8673017cce0c287 completed May 3, 2026, 7:21 a.m.
NED1 Entity disambiguation (via context triple) batch_6a83ac5479dc81908243717e53b43885 completed Aug. 18, 2026, 12:50 a.m.
NEDg Description generation batch_6a83ac9a520c81909a3b0e7d101699bc completed Aug. 18, 2026, 12:51 a.m.
NED2 Entity disambiguation (via description) batch_6a83ad0d82ac8190b0a3a7708e5f7fc4 completed Aug. 18, 2026, 12:53 a.m.
Created at: May 1, 2026, 1:40 a.m.