Triple
T8686770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orma |
E206178
|
entity |
| Predicate | hasGeminateConsonants |
P84187
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Orma, hasGeminateConsonants, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGeminateConsonants Context triple: [Orma, hasGeminateConsonants, yes]
-
A.
hasConsonantHarmony
Indicates that the entities are related by a pattern where consonants within a linguistic unit adjust to share similar features, creating consonant harmony.
-
B.
hasNasalConsonants
Indicates that the subject language or word includes one or more nasal consonant sounds in its phonological inventory or pronunciation.
-
C.
hasConsonantClusters
Indicates that the subject contains sequences of two or more consonants occurring together without intervening vowels.
-
D.
hasConsonantSigns
Indicates that one entity possesses or includes consonant sign characters as part of its representation or structure.
-
E.
supportsConjunctConsonants
Indicates that a writing system or orthographic convention allows the formation and use of conjunct consonant clusters (combined consonant characters).
- 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_69ca835481fc819084e33d3bc883bfa6 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5730309081909a9a0256c9bf5f8f |
completed | March 31, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69cc4569f9048190b9c86b4c81103d35 |
completed | March 31, 2026, 10:06 p.m. |
| PDg | Predicate description generation | batch_69cc483f06f48190879f4702c8b4ed00 |
completed | March 31, 2026, 10:18 p.m. |
Created at: March 30, 2026, 6:33 p.m.