Triple

T5665694
Position Surface form Disambiguated ID Type / Status
Subject East Frisian Low Saxon E124850 entity
Predicate hasVarietyWithin P41829 FINISHED
Object urban East Frisian Low Saxon 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: urban East Frisian Low Saxon | Statement: [East Frisian Low Saxon, hasVarietyWithin, urban East Frisian Low Saxon]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasVarietyWithin
Context triple: [East Frisian Low Saxon, hasVarietyWithin, urban East Frisian Low Saxon]
  • A. hasApproximateNumberOfVarieties
    Indicates that an entity is associated with an estimated or non-exact count of different varieties or types.
  • B. hasNeighboringVariety
    Indicates that one variety is geographically or spatially adjacent to another variety.
  • C. varietyOf chosen
    Indicates that one entity is a specific type, kind, or variant of another, more general entity.
  • D. hasVariability
    Indicates that an entity exhibits variation or fluctuation in its state, value, or characteristics over time or across instances.
  • E. standardVarietyBasedIn
    Indicates that a standard or reference variety (such as a language or dialect) is primarily established, recognized, or centered in a particular location or region.
  • 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_69c00828906881908966f270b8f130cf completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c0236d3f94819095111c41a323612d completed March 22, 2026, 5:14 p.m.
PD Predicate disambiguation batch_69c021ba4ec481909db8cdbf0e907dd6 completed March 22, 2026, 5:07 p.m.
Created at: March 22, 2026, 3:43 p.m.