Triple

T24731074
Position Surface form Disambiguated ID Type / Status
Subject Korandje language E618288 entity
Predicate hasSignificantContactWith P4255 FINISHED
Object Songhay 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: Songhay languages | Statement: [Korandje language, hasSignificantContactWith, Songhay languages]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasSignificantContactWith
Context triple: [Korandje language, hasSignificantContactWith, Songhay languages]
  • A. historicalContactWith chosen
    Indicates that two entities have interacted or been in communication with each other at some point in the past.
  • B. hasContactTracingActivities
    Indicates that an entity engages in or is associated with activities related to tracking and monitoring contacts of individuals, typically for disease exposure or transmission analysis.
  • C. hasQuarantine
    Indicates that an entity is subject to, or associated with, a quarantine condition or period.
  • D. hasSignificant
    Indicates that one entity possesses or exhibits a level of importance, impact, or relevance that is notably large or meaningful in relation to another entity or context.
  • E. timeOfNotableContact
    Indicates the specific time at which a notable or significant contact or interaction between entities occurred.
  • 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_69e2fab772608190b74163751047ff50 completed April 18, 2026, 3:29 a.m.
NER Named-entity recognition batch_69f44a417a58819081777e18dda149fd completed May 1, 2026, 6:37 a.m.
PD Predicate disambiguation batch_69f442a977b08190b44eac040cb90211 completed May 1, 2026, 6:05 a.m.
Created at: April 18, 2026, 4:02 a.m.