Triple
T21217080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Akhuryan River |
E522863
|
entity |
| Predicate | languageNameArmenian |
P48063
|
FINISHED |
| Object | Ախուրյան |
—
|
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: Ախուրյան | Statement: [Akhuryan River, languageNameArmenian, Ախուրյան]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageNameArmenian Context triple: [Akhuryan River, languageNameArmenian, Ախուրյան]
-
A.
nameInArmenian
chosen
Indicates that an entity is identified by a specific name expressed in the Armenian language.
-
B.
officialNameInArmenian
Indicates the officially recognized name of an entity as expressed in the Armenian language.
-
C.
historicalNameInArmenian
Indicates that an entity has a specific historical name or designation when expressed in the Armenian language.
-
D.
languageNameAmharic
Indicates that the subject’s language name is expressed in the Amharic language.
-
E.
hasNameInAzerbaijani
Indicates that an entity is known by a specific name when expressed in the Azerbaijani language.
- 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_69e0b511ed84819099b449b4a111085c |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e734744dcc81908b3065adc93b4b98 |
completed | April 21, 2026, 8:25 a.m. |
| PD | Predicate disambiguation | batch_69e5f60e1a888190ba75e2e900270a4e |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:41 p.m.