Triple

T28456728
Position Surface form Disambiguated ID Type / Status
Subject Paredes de Coura E716732 entity
Predicate locatedOnRiver P165 FINISHED
Object Coura River
The Coura River is a watercourse in northern Portugal that flows through the municipality of Paredes de Coura before joining the Minho River near the Spanish border.
 E2293745 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: Coura River | Statement: [Paredes de Coura, locatedOnRiver, Coura 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: Coura River
Triple: [Paredes de Coura, locatedOnRiver, Coura River]
Generated description
The Coura River is a watercourse in northern Portugal that flows through the municipality of Paredes de Coura before joining the Minho River near the Spanish border.

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_69efd6b76f8c8190a7ba908aca280942 completed April 27, 2026, 9:35 p.m.
NER Named-entity recognition batch_69f64e76937c8190aa7cb4ab1fc4ca98 completed May 2, 2026, 7:20 p.m.
NED1 Entity disambiguation (via context triple) batch_6a7afab5ce3c8190819281618af89f94 completed Aug. 11, 2026, 10:34 a.m.
NEDg Description generation batch_6a7afb242f2c8190a39accb0832dade3 completed Aug. 11, 2026, 10:36 a.m.
NED2 Entity disambiguation (via description) batch_6a7afbd7bb808190963112b3c30947c1 completed Aug. 11, 2026, 10:39 a.m.
Created at: April 28, 2026, 1:54 a.m.