Triple

T33867051
Position Surface form Disambiguated ID Type / Status
Subject Kamboja–Gandhara region E868086 entity
Predicate languageContactAreaFor P17400 FINISHED
Object Indo-Aryan languages 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: Indo-Aryan languages | Statement: [Kamboja–Gandhara region, languageContactAreaFor, Indo-Aryan languages]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: languageContactAreaFor
Context triple: [Kamboja–Gandhara region, languageContactAreaFor, Indo-Aryan languages]
  • A. languageContactWith
    Indicates a relationship where two or more languages come into contact through their speakers, leading to interaction and potential mutual influence.
  • B. languageArea
    Indicates the geographic or cultural region in which a particular language is used or predominantly spoken.
  • C. linguisticArea chosen
    Indicates a regional context in which languages share features due to geographic proximity and contact rather than common genetic origin.
  • D. linguisticStatusOfArea
    Indicates the linguistic status or condition that characterizes a particular geographic area.
  • E. nationalLanguageContact
    Indicates that there is a relationship of linguistic contact or interaction between a national language and another language or language community.
  • 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_69f34995029081909ede0f7df73d1a5e completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_6a0041860fd081908623ef9fd40a9775 completed May 10, 2026, 8:27 a.m.
PD Predicate disambiguation batch_6a00414b01488190a312adb3b25d69cf completed May 10, 2026, 8:26 a.m.
Created at: May 1, 2026, 1:47 a.m.