Triple

T4178667
Position Surface form Disambiguated ID Type / Status
Subject Veluws E86538 entity
Predicate hasCodeIn P54244 FINISHED
Object classified under Dutch Low Saxon in ISO 639-3 (nds-nl) 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: classified under Dutch Low Saxon in ISO 639-3 (nds-nl) | Statement: [Veluws, hasCodeIn, classified under Dutch Low Saxon in ISO 639-3 (nds-nl)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasCodeIn
Context triple: [Veluws, hasCodeIn, classified under Dutch Low Saxon in ISO 639-3 (nds-nl)]
  • A. hasCodeContext
    Indicates that an entity is associated with or occurs within a particular programming or code-related context.
  • B. hasProgramCode
    Indicates that an entity is associated with a specific program identifier or code used to reference or classify it within a system.
  • C. hasCodeLetters
    Indicates that an entity is associated with, or represented by, a specific sequence of letters used as its code or identifier.
  • D. codeFor
    Indicates that one entity serves as the implementation, encoding, or programmatic representation for another entity.
  • E. hasFeatureCode
    Indicates that an entity is associated with a specific feature identifier or code that characterizes one of its properties or attributes.
  • F. None of above. chosen

Provenance (4 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_69aed93de98c8190ad838ce507b77c8a completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69af07078cb081909f64326b12522410 completed March 9, 2026, 5:44 p.m.
PD Predicate disambiguation batch_69af019155448190b19868583272513f completed March 9, 2026, 5:21 p.m.
PDg Predicate description generation batch_69af07059d288190a1ea79449414fbce completed March 9, 2026, 5:44 p.m.
Created at: March 9, 2026, 3:45 p.m.