Triple
T28945158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Hill |
E730558
|
entity |
| Predicate | hasNameInArmenianScript |
P48063
|
FINISHED |
| Object | Կարմիր Բլուր |
—
|
NE NERFINISHED |
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: [Red Hill, hasNameInArmenianScript, Կարմիր Բլուր]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNameInArmenianScript Context triple: [Red Hill, hasNameInArmenianScript, Կարմիր Բլուր]
-
A.
nameInArmenian
chosen
Indicates that an entity is identified by a specific name expressed in the Armenian language.
-
B.
hasNameInAzerbaijani
Indicates that an entity is known by a specific name when expressed in the Azerbaijani language.
-
C.
hasNameInArabic
Indicates that an entity is associated with a specific name expressed in the Arabic language.
-
D.
hasNameInUyghur
Indicates that an entity is associated with a specific name expressed in the Uyghur language.
-
E.
hasNameInHebrew
Indicates that an entity is associated with a specific name expressed in the Hebrew 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_69f043ea0aa88190a25acbf46157995a |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69fd474b7e788190a9bb9b542d878f60 |
completed | May 8, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69fd46d8b2f0819099d92d72c902f60e |
completed | May 8, 2026, 2:13 a.m. |
Created at: April 28, 2026, 8:39 a.m.