Triple

T23453283
Position Surface form Disambiguated ID Type / Status
Subject Doubs E567843 entity
Predicate hasCity P316 FINISHED
Object Baume-les-Dames
Baume-les-Dames is a small historic commune in eastern France’s Bourgogne-Franche-Comté region, known for its picturesque setting in the Doubs valley and surrounding limestone cliffs.
E1644454 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: Baume-les-Dames | Statement: [Doubs, hasCity, Baume-les-Dames]
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: Baume-les-Dames
Triple: [Doubs, hasCity, Baume-les-Dames]
Generated description
Baume-les-Dames is a small historic commune in eastern France’s Bourgogne-Franche-Comté region, known for its picturesque setting in the Doubs valley and surrounding limestone cliffs.

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_69e2458b4c888190b1d7998f9862a558 completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f1a694f19081909117bc9b10ca8a83 completed April 29, 2026, 6:35 a.m.
NED1 Entity disambiguation (via context triple) batch_6a10044b44108190b3a6a9bc1bdf41ae completed May 22, 2026, 7:22 a.m.
NEDg Description generation batch_6a100710ac5081908fe0e6c9ff7a2273 completed May 22, 2026, 7:34 a.m.
NED2 Entity disambiguation (via description) batch_6a1007a4b0a08190ad91e9c327c2ff65 completed May 22, 2026, 7:37 a.m.
Created at: April 17, 2026, 5:52 p.m.