Triple

T33288861
Position Surface form Disambiguated ID Type / Status
Subject Atlas Berber E852259 entity
Predicate standardizedVarietyOf P41829 FINISHED
Object Standard Moroccan Amazigh NE NERFINISHED

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: Standard Moroccan Amazigh | Statement: [Atlas Berber, standardizedVarietyOf, Standard Moroccan Amazigh]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: standardizedVarietyOf
Context triple: [Atlas Berber, standardizedVarietyOf, Standard Moroccan Amazigh]
  • A. hasNonStandardizedVarieties
    Indicates that an entity possesses forms or variants that are not governed by a uniform or officially established standard.
  • B. 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.
  • C. varietyOf chosen
    Indicates that one entity is a specific type, kind, or variant of another, more general entity.
  • D. hasVarietyOf
    Indicates that an entity possesses or offers multiple different types, forms, or versions of something.
  • E. standardizedBy
    Indicates that one entity defines, regulates, or formalizes the standards or specifications by which another entity is created, measured, or operated.
  • 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_69f349660ff48190a4568803d0b89941 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69fbad1e94988190b86d447a68e65067 completed May 6, 2026, 9:05 p.m.
PD Predicate disambiguation batch_69fba881b8e0819094790935152b99a1 completed May 6, 2026, 8:45 p.m.
Created at: May 1, 2026, 1:32 a.m.