Triple

T5732065
Position Surface form Disambiguated ID Type / Status
Subject Puquina language E126406 entity
Predicate possibleDescendant P66151 FINISHED
Object Callahuaya language 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: Callahuaya language | Statement: [Puquina language, possibleDescendant, Callahuaya language]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: possibleDescendant
Context triple: [Puquina language, possibleDescendant, Callahuaya language]
  • A. possibleRelative
    Indicates a relationship where one entity may be related to another by family or kinship, but the exact nature of the relationship is uncertain or not fully established.
  • B. ancestorDescribedAs
    Indicates that an ancestor is characterized or referred to using a particular description, label, or portrayal.
  • C. possibleFamily
    Indicates that two entities could plausibly be related as members of the same family, though the familial relationship is not confirmed.
  • D. possibleMother
    Indicates that one entity could be the biological or adoptive mother of another, but this relationship is uncertain or not definitively established.
  • E. descentFrom
    Indicates that one entity is a descendant of another, typically through a lineage or ancestral relationship.
  • 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_69c0083082288190b7478cead6b5430a completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c029014588819094a2a0f6f9b66bab completed March 22, 2026, 5:38 p.m.
PD Predicate disambiguation batch_69c021c6488881909bed4a4534d57f70 completed March 22, 2026, 5:07 p.m.
PDg Predicate description generation batch_69c028fec2bc819083f5dca6a8d9d435 completed March 22, 2026, 5:38 p.m.
Created at: March 22, 2026, 3:47 p.m.