Triple

T5961997
Position Surface form Disambiguated ID Type / Status
Subject Badiot E132659 entity
Predicate hasISO639Status P25082 FINISHED
Object no separate ISO 639 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: no separate ISO 639 code | Statement: [Badiot, hasISO639Status, no separate ISO 639 code]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasISO639Status
Context triple: [Badiot, hasISO639Status, no separate ISO 639 code]
  • A. ISO639Status chosen
    Indicates the classification of a language’s status according to the ISO 639 standard (e.g., whether and how it is recognized or coded in that system).
  • B. hasISO6393Code
    Indicates that a language or linguistic entity is associated with a specific ISO 639-3 three-letter language code.
  • C. hasISO639_5Code
    Indicates that a language or language group is associated with a specific ISO 639-5 code that identifies it within the ISO 639-5 language classification standard.
  • D. ISO639_3Status
    Indicates the classification or status assigned to a language according to the ISO 639-3 standard (e.g., active, extinct, historical, constructed).
  • E. hasLanguageStatus
    Indicates that an entity has a particular status or condition regarding its language use, recognition, or classification.
  • 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_69c0086c2364819091e9fe2f58fa2517 completed March 22, 2026, 3:19 p.m.
NER Named-entity recognition batch_69c03fb7f8a88190a8bd45208bda4a03 completed March 22, 2026, 7:15 p.m.
PD Predicate disambiguation batch_69c0335a635881909c58c1ef0f97f1e8 completed March 22, 2026, 6:22 p.m.
Created at: March 22, 2026, 4:02 p.m.