Triple
T579665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Estonian language |
E15029
|
entity |
| Predicate | hasVowelHarmony |
P15727
|
FINISHED |
| Object | partially |
—
|
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: partially | Statement: [Estonian language, hasVowelHarmony, partially]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVowelHarmony Context triple: [Estonian language, hasVowelHarmony, partially]
-
A.
hasNasalVowels
Indicates that the subject language or phonological system includes vowels that are produced with nasal airflow (nasalized vowels).
-
B.
hasVowelNotationSystem
Indicates that a writing or transcription system for a language includes a method for explicitly representing vowel sounds.
-
C.
hasVowelLengthContrast
Indicates that a language distinguishes word meanings based on differences in the length (duration) of vowel sounds.
-
D.
hasSyllabary
Indicates that one entity possesses or is associated with a specific syllabary writing system used to represent its language or notation.
-
E.
hasPhonemicTone
Indicates that a language, word, or syllable uses pitch differences (tones) as phonemic contrasts that can change meaning.
- 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_69a4935783b8819082b77726ec10cc42 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49b6c358081908f458b9e3e208c0d |
completed | March 1, 2026, 8:02 p.m. |
| PD | Predicate disambiguation | batch_69a494c692288190b88f30299516b5ba |
completed | March 1, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69a4985a2d08819090947895d9439e06 |
completed | March 1, 2026, 7:49 p.m. |
Created at: March 1, 2026, 7:33 p.m.