Triple

T36251850
Position Surface form Disambiguated ID Type / Status
Subject Cahuapanan–Jivaroan hypothesis E891822 entity
Predicate hasUncertainValidity P193749 FINISHED
Object true 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: true | Statement: [Cahuapanan–Jivaroan hypothesis, hasUncertainValidity, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasUncertainValidity
Context triple: [Cahuapanan–Jivaroan hypothesis, hasUncertainValidity, true]
  • A. hasUncertainty
    Indicates that the relationship or value is associated with some level or type of uncertainty rather than being fully definite or precise.
  • B. hasUncertainForm
    Indicates that the form or structure of something is not clearly defined, fixed, or confidently known.
  • C. hasUncertaintyReason
    Indicates that there is a specific reason or explanation for why something is uncertain or not known with confidence.
  • D. hasUncertainParameters
    Indicates that the relationship or action involves parameters whose values, conditions, or characteristics are not fully known, fixed, or reliably determined.
  • E. hasUncertainNature
    Indicates that the nature, status, or characteristics of the relationship or situation are not clearly defined, known, or determined.
  • F. None of above. chosen

Provenance (4 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_69f76e4599108190811532e707d6bc2c completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69fd509e6bc08190b263923c2f40fea3 completed May 8, 2026, 2:55 a.m.
PD Predicate disambiguation batch_69fd4fd1a58881909d4b84de1b24e380 completed May 8, 2026, 2:52 a.m.
PDg Predicate description generation batch_69fd509cdc5c8190a5f2c451bc0d0b25 completed May 8, 2026, 2:55 a.m.
Created at: May 3, 2026, 4:09 p.m.