Triple

T8582788
Position Surface form Disambiguated ID Type / Status
Subject Badînî E203223 entity
Predicate sharesFeatureWithKurmanji P5696 FINISHED
Object ergative alignment in past transitive constructions 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: ergative alignment in past transitive constructions | Statement: [Badînî, sharesFeatureWithKurmanji, ergative alignment in past transitive constructions]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: sharesFeatureWithKurmanji
Context triple: [Badînî, sharesFeatureWithKurmanji, ergative alignment in past transitive constructions]
  • A. sharesFeatureWith chosen
    Indicates that two entities have at least one common attribute, property, or characteristic in common.
  • B. sharesTjukurpaWith
    Indicates that one entity shares or transmits Tjukurpa (sacred law, stories, or spiritual knowledge) with another entity.
  • C. sharesLanguageWith
    Indicates that two entities use at least one common language for communication.
  • D. shareFeature
    Indicates that two or more entities possess at least one common attribute, property, or characteristic.
  • E. sharesUniverseWith
    Indicates that two entities exist within the same fictional or narrative universe, implying shared continuity, setting, or canon.
  • 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_69ca8329bb7c8190a63c643730839103 completed March 30, 2026, 2:05 p.m.
NER Named-entity recognition batch_69cbeb1d0edc8190b4495935275252f3 completed March 31, 2026, 3:41 p.m.
PD Predicate disambiguation batch_69cbd11b13108190b07f8f161425a585 completed March 31, 2026, 1:50 p.m.
Created at: March 30, 2026, 6:22 p.m.