Triple
T31550820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Homshetsi |
E804993
|
entity |
| Predicate | phonologyRelatedTo |
P50775
|
FINISHED |
| Object | Western Armenian phonology |
—
|
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: Western Armenian phonology | Statement: [Homshetsi, phonologyRelatedTo, Western Armenian phonology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: phonologyRelatedTo Context triple: [Homshetsi, phonologyRelatedTo, Western Armenian phonology]
-
A.
phonologyRelation
chosen
Indicates a relationship between linguistic elements based on their phonological properties, such as sound patterns, features, or structures.
-
B.
hasPhonologicalBasisFor
Indicates that one entity serves as the phonological source, motivation, or foundation for another entity.
-
C.
hasPhonologicalDescription
Indicates that an entity is associated with a specific representation or description of its sound structure or phonological form.
-
D.
hasPhonologicalParameters
Indicates that an entity is associated with specific phonological features or parameters that characterize its sound structure.
-
E.
hasOwnPhonology
Indicates that an entity possesses its own distinct phonological system or set of sound patterns, separate from those of other entities.
- 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_69f348d11a048190a65eb8384a3754ac |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a8055f8081908f635fe04654b5fe |
completed | May 3, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69f6a75656e081908739ed9e2f600e42 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 10:11 p.m.