Triple

T32811946
Position Surface form Disambiguated ID Type / Status
Subject Kolya E839176 entity
Predicate stressPatternInRussian P4253 FINISHED
Object stress on first syllable 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: stress on first syllable | Statement: [Kolya, stressPatternInRussian, stress on first syllable]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: stressPatternInRussian
Context triple: [Kolya, stressPatternInRussian, stress on first syllable]
  • A. hasStressPattern chosen
    Indicates that an entity (such as a word or phrase) follows a particular arrangement of stressed and unstressed units (e.g., syllables) in its pronunciation.
  • B. inscriptionTextRussian
    Indicates that the associated inscription or written text is expressed in the Russian language.
  • C. phoneticPattern
    Indicates that two or more linguistic elements share a specific arrangement or sequence of sounds according to a defined phonological structure.
  • D. hasRussianVersion
    Indicates that something has a corresponding version or counterpart that is in the Russian language.
  • E. hasSyllableStructureTendency
    Indicates a tendency or preference for a particular syllable structure pattern in how something (e.g., a language or speaker) organizes syllables.
  • 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_69f3493d35208190b4351b4e85f2fa16 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f6ce6d659881909ddcec1d2966e020 completed May 3, 2026, 4:26 a.m.
PD Predicate disambiguation batch_69f6cc1667a48190b42684f6ec22dae9 completed May 3, 2026, 4:16 a.m.
Created at: May 1, 2026, 1:15 a.m.