Triple
T23781209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tiberian vowel points |
E587817
|
entity |
| Predicate | positionRelativeToConsonants |
P45435
|
FINISHED |
| Object | below consonants |
—
|
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: below consonants | Statement: [Tiberian vowel points, positionRelativeToConsonants, below consonants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionRelativeToConsonants Context triple: [Tiberian vowel points, positionRelativeToConsonants, below consonants]
-
A.
hasConsonantPlace
Indicates that a consonant sound is articulated at a particular place of articulation in the vocal tract.
-
B.
vowelPlacement
chosen
Indicates the relative position or arrangement of vowel sounds within a linguistic unit, such as a word or syllable.
-
C.
placeOfArticulation
Indicates the specific location within the vocal tract where a speech sound is produced.
-
D.
phonologyRelation
Indicates a relationship between linguistic elements based on their phonological properties, such as sound patterns, features, or structures.
-
E.
hasNasalConsonants
Indicates that the subject language or word includes one or more nasal consonant sounds in its phonological inventory or pronunciation.
- 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_69e2490f4ad48190b690878eec3596c6 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1c62bef608190b75afa6bf4024ae3 |
completed | April 29, 2026, 8:49 a.m. |
| PD | Predicate disambiguation | batch_69f155f79e34819080f9ddb972b34deb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:16 p.m.