Triple

T11422778
Position Surface form Disambiguated ID Type / Status
Subject Würm River E270665 entity
Predicate hasDiacriticInName P2270 FINISHED
Object ü LITERAL 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: ü | Statement: [Würm River, hasDiacriticInName, ü]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasDiacriticInName
Context triple: [Würm River, hasDiacriticInName, ü]
  • A. usesDiacritics chosen
    Indicates that the referenced text or linguistic element employs diacritical marks as part of its written form.
  • B. usesDiacriticsFrom
    Indicates that one entity employs or incorporates the diacritical marks that originate from or are characteristic of another entity.
  • C. hasUnicodeName
    Indicates that an entity is associated with a specific official Unicode name assigned to a character or symbol.
  • D. hasNameInSlavonic
    Indicates that an entity has a specific name or designation expressed in a Slavonic language.
  • E. hasAccent
    Indicates that an entity speaks with or possesses a particular accent or distinctive pronunciation style.
  • F. None of above.

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_69d6aadeef688190874bcecd88b3dd9b completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d801b357e88190ace56d36a945688f completed April 9, 2026, 7:44 p.m.
PD Predicate disambiguation batch_69d7e71436f88190ac7e45a04ea5c987 completed April 9, 2026, 5:51 p.m.
Created at: April 8, 2026, 9:34 p.m.