Triple

T4271554
Position Surface form Disambiguated ID Type / Status
Subject Proto-Turkic E96950 entity
Predicate possibleContactWith P4255 FINISHED
Object Proto-Mongolic (according to some hypotheses) 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: Proto-Mongolic (according to some hypotheses) | Statement: [Proto-Turkic, possibleContactWith, Proto-Mongolic (according to some hypotheses)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: possibleContactWith
Context triple: [Proto-Turkic, possibleContactWith, Proto-Mongolic (according to some hypotheses)]
  • A. contactWith
    Indicates that two entities are in direct or indirect physical or communicative interaction or touch with each other.
  • B. historicalContactWith chosen
    Indicates that two entities have interacted or been in communication with each other at some point in the past.
  • C. contactWithOutsiders
    Indicates that an entity interacts or communicates directly with individuals or groups outside its usual or designated community, organization, or system.
  • D. hasKontakion
    Indicates that an entity is associated with or possesses a specific kontakion, i.e., a particular liturgical hymn or chant.
  • E. possibleRelative
    Indicates a relationship where one entity may be related to another by family or kinship, but the exact nature of the relationship is uncertain or not fully established.
  • 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_69b34543f06c8190915ebb1a4574ffa9 completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b34ffce3d8819083d2278547fa52c1 completed March 12, 2026, 11:45 p.m.
PD Predicate disambiguation batch_69b347faa45481908c19c29fb906dc92 completed March 12, 2026, 11:10 p.m.
Created at: March 12, 2026, 11:07 p.m.