Triple
T23873609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kamchiya Glacier |
E592796
|
entity |
| Predicate | hasBulgarianName |
P41322
|
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: [Kamchiya Glacier, hasBulgarianName, ледник Камчия]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBulgarianName Context triple: [Kamchiya Glacier, hasBulgarianName, ледник Камчия]
-
A.
nameInBulgarian
chosen
Indicates that an entity is referred to by a specific name when expressed in the Bulgarian language.
-
B.
hasNameInRusyn
Indicates that an entity has a specific name or label expressed in the Rusyn language.
-
C.
hasNameInBosnianCyrillic
Indicates that an entity is associated with a specific name written in Bosnian Cyrillic script.
-
D.
hasNameInSlavonic
Indicates that an entity has a specific name or designation expressed in a Slavonic language.
-
E.
hasEnglishName
Indicates that an entity is associated with a name expressed in the English 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_69e25d23a5c88190ae3999c70ca15e08 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1cbff91788190b7aabe285014b873 |
completed | April 29, 2026, 9:14 a.m. |
| PD | Predicate disambiguation | batch_69f1614a65a88190bde1efb368a151e4 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:14 p.m.