Triple
T3298871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Geʽez script |
E69281
|
entity |
| Predicate | hasVowelOrdersPerConsonant |
P4430
|
FINISHED |
| Object | 7 |
—
|
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: 7 | Statement: [Geʽez script, hasVowelOrdersPerConsonant, 7]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVowelOrdersPerConsonant Context triple: [Geʽez script, hasVowelOrdersPerConsonant, 7]
-
A.
hasDistinctVowelLetters
Indicates that the subject contains vowel letters that are all different from one another, with no vowel repeated.
-
B.
vowelPlacement
Indicates the relative position or arrangement of vowel sounds within a linguistic unit, such as a word or syllable.
-
C.
hasNumberOfVowelLetters
chosen
Indicates that an entity is associated with a specific count of vowel letters it contains.
-
D.
hasIndependentVowelLetters
Indicates that a writing system includes separate, standalone vowel characters rather than representing vowels only through modifications of consonant letters.
-
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.
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_69ad859e529c8190a404273f53cb487d |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb0a49b748190b6db99a85c3cb3c5 |
completed | March 8, 2026, 5:23 p.m. |
| PD | Predicate disambiguation | batch_69ada42407dc81909f60d7a14e1b7934 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:11 p.m.