Triple

T34685202
Position Surface form Disambiguated ID Type / Status
Subject Canton of Raetia (Helvetic Republic) E890723 entity
Predicate alsoKnownAs P39 FINISHED
Object Kanton Rätien
Kanton Rätien was a canton of the short-lived Helvetic Republic (1798–1803) located in the region of present-day Graubünden in eastern Switzerland.
E2292469 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: Kanton Rätien | Statement: [Canton of Raetia (Helvetic Republic), alsoKnownAs, Kanton Rätien]
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: Kanton Rätien
Triple: [Canton of Raetia (Helvetic Republic), alsoKnownAs, Kanton Rätien]
Generated description
Kanton Rätien was a canton of the short-lived Helvetic Republic (1798–1803) located in the region of present-day Graubünden in eastern Switzerland.

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_69f349dabc008190a18999c26682ed47 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f7234cdb9c8190a6a46242de1b3926 completed May 3, 2026, 10:28 a.m.
NED1 Entity disambiguation (via context triple) batch_6a799969af6881908fe2ef003d3e30ee completed Aug. 10, 2026, 9:27 a.m.
NEDg Description generation batch_6a799a4dda9c81908d11d515d35c6d48 completed Aug. 10, 2026, 9:30 a.m.
NED2 Entity disambiguation (via description) batch_6a799a9f2f00819098677733c659afe4 completed Aug. 10, 2026, 9:32 a.m.
Created at: May 1, 2026, 2:05 a.m.