Triple

T6773726
Position Surface form Disambiguated ID Type / Status
Subject Lower Carniolan dialect E155102 entity
Predicate usedAsBasisBy P7051 FINISHED
Object codifiers of standard Slovene 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: codifiers of standard Slovene | Statement: [Lower Carniolan dialect, usedAsBasisBy, codifiers of standard Slovene]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usedAsBasisBy
Context triple: [Lower Carniolan dialect, usedAsBasisBy, codifiers of standard Slovene]
  • A. usedAsBasisFor chosen
    Indicates that one entity serves as the foundation, reference, or starting point upon which another entity is developed, derived, justified, or constructed.
  • B. isUsedAs
    Indicates that one entity serves a particular function, role, or purpose as another entity.
  • C. becameBasisOf
    Indicates that one entity served as the foundational source, model, or starting point upon which another entity was developed, derived, or established.
  • D. areUsedBy
    Indicates that certain entities serve as tools, resources, or means that are utilized or employed by other entities.
  • E. isUsedUnder
    Indicates that one entity is utilized or applied within the context, conditions, or framework defined by another entity.
  • 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_69c68812ef7c819099369f51febb725c completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6d24c1b088190b99e9264b9b03dd8 completed March 27, 2026, 6:54 p.m.
PD Predicate disambiguation batch_69c6d094105881909c5806eb4afa6306 completed March 27, 2026, 6:46 p.m.
Created at: March 27, 2026, 2:13 p.m.