Triple

T20933924
Position Surface form Disambiguated ID Type / Status
Subject Proto-Bulgarian E515534 entity
Predicate disputedClassification P50823 FINISHED
Object Turkic vs. Iranic hypotheses 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: Turkic vs. Iranic hypotheses | Statement: [Proto-Bulgarian, disputedClassification, Turkic vs. Iranic hypotheses]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: disputedClassification
Context triple: [Proto-Bulgarian, disputedClassification, Turkic vs. Iranic hypotheses]
  • A. disputed chosen
    Indicates that there is active disagreement or contestation over the validity, ownership, interpretation, or status of the relationship or claim between the entities.
  • B. disputedAspect
    Indicates that a particular feature, detail, or component of something is subject to disagreement or contention between parties.
  • C. notClassifiedAs
    Indicates that an entity is explicitly not assigned to, or excluded from, a particular class or category.
  • D. usuallyClassifiedAs
    Indicates that an entity is most commonly or typically placed into a particular category or type, though other classifications may also exist.
  • E. areClassifiedBy
    Indicates that entities are assigned to one or more categories, types, or classes according to a specified classification scheme.
  • 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_69e0b4fc13408190b06868df03c5c29b completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6f94fc194819099df82357a7f33c7 completed April 21, 2026, 4:13 a.m.
PD Predicate disambiguation batch_69e5c9af1fe08190953366a466950140 completed April 20, 2026, 6:37 a.m.
Created at: April 16, 2026, 12:49 p.m.