Triple
T3725084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lamed |
E81728
|
entity |
| Predicate | isGuttural |
P51246
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [Lamed, isGuttural, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isGuttural Context triple: [Lamed, isGuttural, false]
-
A.
hasNasalVowels
Indicates that the subject language or phonological system includes vowels that are produced with nasal airflow (nasalized vowels).
-
B.
hasEjectiveConsonants
Indicates that a language’s consonant inventory includes ejective consonants, produced with a glottalic egressive airstream mechanism.
-
C.
hasVowelHarmony
Indicates that the phonological vowels in a word or morpheme conform to a systematic harmony pattern (e.g., all front or all back vowels) according to the language’s vowel harmony rules.
-
D.
vocalizationCharacteristic
Indicates how an entity’s vocal sounds are characterized, such as their quality, style, or distinctive acoustic features.
-
E.
hasVowelSystem
Indicates that an entity possesses a particular system or pattern of vowel sounds (a structured set of vowel phonemes or contrasts).
- 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_69ad8b1b7ef081908d2d381bbf54985a |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcaf54af881908bd8d520595de061 |
completed | March 8, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69adc0452f5081909c79e114a86cce8c |
completed | March 8, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69adc226fffc81909c679b44e611fee6 |
completed | March 8, 2026, 6:38 p.m. |
Created at: March 8, 2026, 3:34 p.m.