Triple

T26977791
Position Surface form Disambiguated ID Type / Status
Subject Korandje people E679505 entity
Predicate languageContactZone P17400 FINISHED
Object Berber-Arabic-Songhay contact 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: Berber-Arabic-Songhay contact | Statement: [Korandje people, languageContactZone, Berber-Arabic-Songhay contact]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: languageContactZone
Context triple: [Korandje people, languageContactZone, Berber-Arabic-Songhay contact]
  • A. languageContactWith
    Indicates a relationship where two or more languages come into contact through their speakers, leading to interaction and potential mutual influence.
  • B. linguisticArea chosen
    Indicates a regional context in which languages share features due to geographic proximity and contact rather than common genetic origin.
  • C. regionOfDialectContinuum
    Indicates that a dialect continuum is associated with, or occurs within, a specific geographic region.
  • D. ethnoLinguisticRegionOf
    Indicates that a region is defined or characterized by the shared ethnic and linguistic identity of the group associated with it.
  • E. languageArea
    Indicates the geographic or cultural region in which a particular language is used or predominantly spoken.
  • 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_69fcda3699948190adb57625bae08091 completed May 7, 2026, 6:30 p.m.
PD Predicate disambiguation batch_69fcd8fd16d08190b0aca6e19a632e99 completed May 7, 2026, 6:25 p.m.
Created at: April 27, 2026, 6:43 a.m.