Triple

T32206411
Position Surface form Disambiguated ID Type / Status
Subject Mauke dialect E822682 entity
Predicate isNotStandardizedAs P148225 FINISHED
Object separate ISO 639-3 code 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: separate ISO 639-3 code | Statement: [Mauke dialect, isNotStandardizedAs, separate ISO 639-3 code]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isNotStandardizedAs
Context triple: [Mauke dialect, isNotStandardizedAs, separate ISO 639-3 code]
  • A. notStandardizedBy chosen
    Indicates that an entity has not been brought into conformity with a particular standard, method, or specification by the referenced agent or authority.
  • B. isLessStandardizedThan
    Indicates that one entity follows fewer or less rigid standards, norms, or formalized procedures than another entity.
  • C. isStandard
    Indicates that something conforms to an established norm, specification, or commonly accepted rule.
  • D. isStandardOf
    Indicates that something serves as the recognized norm, reference, or benchmark by which another thing is defined, measured, or evaluated.
  • E. standardizedIn
    Indicates that something has been formally defined, regulated, or made uniform within a particular standard, framework, or jurisdiction.
  • 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_69f349093174819086e633c190a51aa8 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6bb8ac984819098e2660c02662deb completed May 3, 2026, 3:05 a.m.
PD Predicate disambiguation batch_69f6b3aa892481908d29283a074e6722 completed May 3, 2026, 2:32 a.m.
Created at: May 1, 2026, 12:36 a.m.