Triple

T31870552
Position Surface form Disambiguated ID Type / Status
Subject Mohammad E813584 entity
Predicate ISO639-1LanguageCodeOfOrigin P110016 FINISHED
Object ar 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: ar | Statement: [Mohammad, ISO639-1LanguageCodeOfOrigin, ar]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: ISO639-1LanguageCodeOfOrigin
Context triple: [Mohammad, ISO639-1LanguageCodeOfOrigin, ar]
  • A. ISO639Language
    Indicates that an entity is associated with a language identified or classified according to the ISO 639 language code standard.
  • B. ISO639-1Equivalent
    Indicates that two language identifiers are equivalent according to the ISO 639-1 two-letter language code standard.
  • C. ISO639BaseLanguage
    Indicates that one language is the base or primary language from which another language (such as a variant or dialect) is derived or classified in the ISO 639 standard.
  • D. ISO639CollectiveCode
    Indicates that the relationship assigns or associates an ISO 639 collective language code (a code representing a group of related languages) to the relevant language entity or set of languages.
  • E. ISO639-1CodeFor chosen
    Indicates that one entity is the ISO 639-1 two-letter language code corresponding to the language represented by the other entity.
  • 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_69f348ecb07481909c8f72619131b115 completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69f6b09bc8bc81909ca5fb69d9628355 completed May 3, 2026, 2:19 a.m.
PD Predicate disambiguation batch_69f6aca59d4881908d14ed47962703bd completed May 3, 2026, 2:02 a.m.
Created at: April 30, 2026, 11:54 p.m.