Triple

T176764
Position Surface form Disambiguated ID Type / Status
Subject Polish language E3589 entity
Predicate hasPhoneme P7438 FINISHED
Object ł 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: ł | Statement: [Polish language, hasPhoneme, ł]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasPhoneme
Context triple: [Polish language, hasPhoneme, ł]
  • A. hasPhonemicContrast
    Indicates that two or more speech sounds are distinguished in a language by differences that change word meaning.
  • B. hasNumberOfConsonantLetters
    Indicates the relationship between an entity and the count of consonant letters present in its written form.
  • C. hasStressPattern
    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.
  • D. hasNumberOfVowelLetters
    Indicates that an entity is associated with a specific count of vowel letters it contains.
  • E. hasRomanizationOf
    Indicates that one entity is a romanized representation (written in the Latin alphabet) of the other entity’s original script form.
  • F. None of above. chosen

Provenance (4 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_69a25374990081909766d30c79a18e0e completed Feb. 28, 2026, 2:31 a.m.
NER Named-entity recognition batch_69a258fd278481908ad4498e03f38e2f completed Feb. 28, 2026, 2:54 a.m.
PD Predicate disambiguation batch_69a25669d99481908c5e82ba8641205a completed Feb. 28, 2026, 2:43 a.m.
PDg Predicate description generation batch_69a258b30f6c8190be2181f30c40e04d completed Feb. 28, 2026, 2:53 a.m.
Created at: Feb. 28, 2026, 2:39 a.m.