Triple

T25766842
Position Surface form Disambiguated ID Type / Status
Subject Teiwa language E648904 entity
Predicate hasBasicClauseType P58758 FINISHED
Object transitive and intransitive clauses 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: transitive and intransitive clauses | Statement: [Teiwa language, hasBasicClauseType, transitive and intransitive clauses]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasBasicClauseType
Context triple: [Teiwa language, hasBasicClauseType, transitive and intransitive clauses]
  • A. hasClauseStructure
    Indicates that one linguistic unit exhibits a particular internal clause configuration or pattern in relation to another specified clause structure.
  • B. typeOfClause chosen
    Indicates the specific kind or category of clause that a given clause instance belongs to.
  • C. hasBasicUnit
    Indicates that one entity is composed of, defined by, or fundamentally characterized through another entity that serves as its basic or minimal unit.
  • D. hasCriterionType
    Indicates that something is associated with or classified by a specific type of criterion used for evaluation or decision-making.
  • E. hasStandardType
    Indicates that something conforms to or is categorized under a defined standard classification or type.
  • 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_69e7ab322db0819092d6a2b3d4572e01 completed April 21, 2026, 4:52 p.m.
NER Named-entity recognition batch_69f63fd6c68481908c542aa03e297b9c completed May 2, 2026, 6:17 p.m.
PD Predicate disambiguation batch_69f63c6456608190b94e7c2e2c2a4824 completed May 2, 2026, 6:03 p.m.
Created at: April 22, 2026, 5:11 a.m.