Triple

T5667350
Position Surface form Disambiguated ID Type / Status
Subject Colorado River Numic E124887 entity
Predicate isoClassification P24573 FINISHED
Object Numic subgroup of Uto-Aztecan 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: Numic subgroup of Uto-Aztecan | Statement: [Colorado River Numic, isoClassification, Numic subgroup of Uto-Aztecan]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isoClassification
Context triple: [Colorado River Numic, isoClassification, Numic subgroup of Uto-Aztecan]
  • A. isoClassificationStatus
    Indicates the current status or stage of an entity within an ISO-based classification or standardization process.
  • B. securityClassification
    Indicates the level or category of security sensitivity or access restriction assigned to an entity.
  • C. isoStatus
    Indicates the ISO (International Organization for Standardization) compliance or certification status associated with an entity or process.
  • D. isClassifiedUnder chosen
    Indicates that one entity is categorized or grouped within a broader class, type, or category represented by another entity.
  • E. areClassifiedBy
    Indicates that entities are assigned to one or more categories, types, or classes according to a specified classification scheme.
  • 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_69c00828906881908966f270b8f130cf completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c0236d3f94819095111c41a323612d completed March 22, 2026, 5:14 p.m.
PD Predicate disambiguation batch_69c021ba4ec481909db8cdbf0e907dd6 completed March 22, 2026, 5:07 p.m.
Created at: March 22, 2026, 3:43 p.m.