Triple

T1216477
Position Surface form Disambiguated ID Type / Status
Subject Ahirani E26116 entity
Predicate hasPhonologicalFeatures P7162 FINISHED
Object distinct from standard Marathi 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: distinct from standard Marathi | Statement: [Ahirani, hasPhonologicalFeatures, distinct from standard Marathi]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasPhonologicalFeatures
Context triple: [Ahirani, hasPhonologicalFeatures, distinct from standard Marathi]
  • A. hasPhonologicalType
    Indicates that one entity is characterized by or classified as having a particular phonological type (e.g., in terms of sound structure or phonological category).
  • B. hasPhoneme
    Indicates that a linguistic unit (such as a word or morpheme) contains or includes a particular phoneme as part of its sound structure.
  • C. hasPhonemicContrast
    Indicates that two or more speech sounds are distinguished in a language by differences that change word meaning.
  • D. hasLinguisticFeature chosen
    Indicates that an entity possesses a particular linguistic property, trait, or characteristic.
  • E. hasPhonemeInventory
    Indicates that an entity possesses a specific set or system of distinct speech sounds (phonemes) used in its language.
  • 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_69a4948331fc8190b531ac9bec71c491 completed March 1, 2026, 7:33 p.m.
NER Named-entity recognition batch_69a4be059c5c8190a200f09442c22334 completed March 1, 2026, 10:30 p.m.
PD Predicate disambiguation batch_69a4bb62a7c08190a79dcb6ff72ac99b completed March 1, 2026, 10:19 p.m.
Created at: March 1, 2026, 7:46 p.m.