Triple

T11788919
Position Surface form Disambiguated ID Type / Status
Subject Romansh people E280340 entity
Predicate hasDialect P4251 FINISHED
Object Puter E120225 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: Puter | Statement: [Romansh people, hasDialect, Puter]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Puter
Context triple: [Romansh people, hasDialect, Puter]
  • A. Puter chosen
    Puter is one of the main regional dialects of the Romansh language, traditionally spoken in parts of the Engadine valley in Switzerland.
  • B. Iputinga
    Iputinga is a neighborhood located in the city of Recife, in the state of Pernambuco, Brazil.
  • C. Teclea
    Teclea is a genus of flowering plants in the citrus family Rutaceae, native to parts of Africa and known for its aromatic foliage.
  • D. Komptur
    Komptur is an alternative spelling of "Komtur," a historical title used for a commander or head of a local administrative unit in medieval military orders such as the Teutonic Knights.
  • E. Anytos
    Anytos is a figure from Greek mythology known primarily as a Titan or divine guardian associated with the Arcadian goddess Despoina.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69d6ab258b808190b1735835c841e3a4 completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d8a587c2d881909297c3a6c7d26080 completed April 10, 2026, 7:23 a.m.
NED1 Entity disambiguation (via context triple) batch_69f090f62bdc8190a8fd145839aef554 completed April 28, 2026, 10:50 a.m.
Created at: April 8, 2026, 9:42 p.m.