Triple

T26977145
Position Surface form Disambiguated ID Type / Status
Subject Ollari E679487 entity
Predicate neighboringMajorLanguage P16383 FINISHED
Object Odia NE NERFINISHED

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: Odia | Statement: [Ollari, neighboringMajorLanguage, Odia]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: neighboringMajorLanguage
Context triple: [Ollari, neighboringMajorLanguage, Odia]
  • A. hasNeighboringLanguages chosen
    Indicates that two languages are geographically or regionally adjacent to each other in their areas of use.
  • B. neighboringLanguageFamilies
    Indicates that two language families are geographically adjacent or border each other in their primary regions of use.
  • C. hasNeighboringLanguageCommunity
    Indicates that one language community is geographically or socially adjacent to another, allowing for direct contact or interaction between them.
  • D. hasDominantNeighborLanguage
    Indicates that an entity’s primary neighboring language exerts a dominant influence or holds a superior status over other nearby languages.
  • E. closelyAssociatedLanguage
    Indicates that one language is closely connected to another, such as through frequent co-use, mutual influence, or strong cultural or regional association.
  • 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_69eeeb507a7081909d516e1fa08b7d29 completed April 27, 2026, 4:51 a.m.
NER Named-entity recognition batch_69f65f7731e4819099d5bd3d915ee266 completed May 2, 2026, 8:32 p.m.
PD Predicate disambiguation batch_69f65c1f94ac8190bc6fbc7916fc0d82 completed May 2, 2026, 8:18 p.m.
Created at: April 27, 2026, 6:43 a.m.