Triple

T20109808
Position Surface form Disambiguated ID Type / Status
Subject Proto-Haida E490296 entity
Predicate hasReconstructedPhonology P66751 FINISHED
Object yes 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: yes | Statement: [Proto-Haida, hasReconstructedPhonology, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasReconstructedPhonology
Context triple: [Proto-Haida, hasReconstructedPhonology, yes]
  • A. hasLexicalReconstruction
    Indicates that there exists a hypothesized or reconstructed lexical form corresponding to a word or expression, typically inferred for an earlier or unattested stage of a language.
  • B. hasPhonologicalChange
    Indicates a relationship where one linguistic form undergoes a change in its sound structure relative to another form or earlier state.
  • C. hasOwnPhonology
    Indicates that an entity possesses its own distinct phonological system or set of sound patterns, separate from those of other entities.
  • D. hasPhonologicalBasisFor
    Indicates that one entity serves as the phonological source, motivation, or foundation for another entity.
  • E. hasPhonologicalDescription chosen
    Indicates that an entity is associated with a specific representation or description of its sound structure or phonological form.
  • 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_69da62636cc08190982cc71733a17b8d completed April 11, 2026, 3:01 p.m.
NER Named-entity recognition batch_69e666df1b148190a28ead2f7cce7aab completed April 20, 2026, 5:48 p.m.
PD Predicate disambiguation batch_69e54cf788188190a46cc49c9ce7617f completed April 19, 2026, 9:45 p.m.
Created at: April 11, 2026, 11:28 p.m.