Triple

T28419578
Position Surface form Disambiguated ID Type / Status
Subject Arrondissement of Dinant E719903 entity
Predicate containsAdministrativeTerritorialEntity P747 FINISHED
Object Bièvre
Bièvre is a rural municipality in the Walloon region of Belgium, known for its forests, small villages, and location in the province of Namur.
E1893173 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: Bièvre | Statement: [Arrondissement of Dinant, containsAdministrativeTerritorialEntity, Bièvre]
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: Bièvre
Triple: [Arrondissement of Dinant, containsAdministrativeTerritorialEntity, Bièvre]
Generated description
Bièvre is a rural municipality in the Walloon region of Belgium, known for its forests, small villages, and location in the province of Namur.

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_69eff6f1c5088190bc24bfbf92f9c017 completed April 27, 2026, 11:53 p.m.
NER Named-entity recognition batch_69f64dc5440c81908d4a4cda50011f1a completed May 2, 2026, 7:17 p.m.
NED1 Entity disambiguation (via context triple) batch_6a2713ec7ca88190b08d9d85c46060d5 completed June 8, 2026, 7:11 p.m.
NEDg Description generation batch_6a271498c12c81909a3ca72cfeb8bcb5 completed June 8, 2026, 7:14 p.m.
NED2 Entity disambiguation (via description) batch_6a2719a575388190baec154da1d3ed1a completed June 8, 2026, 7:36 p.m.
Created at: April 28, 2026, 1:32 a.m.