Triple
T23873594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kamchiya Glacier |
E592796
|
entity |
| Predicate | countryOfNameOrigin |
P63295
|
FINISHED |
| Object | Bulgaria |
—
|
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: Bulgaria | Statement: [Kamchiya Glacier, countryOfNameOrigin, Bulgaria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryOfNameOrigin Context triple: [Kamchiya Glacier, countryOfNameOrigin, Bulgaria]
-
A.
hasNameOrigin
Indicates that the origin or source of an entity’s name is specified by the related entity.
-
B.
countryOfNamingTradition
chosen
Indicates the country whose cultural or linguistic naming conventions are used to form or interpret a given name.
-
C.
hasNameEtymologyIn
Indicates that the origin or derivation of an entity’s name is based in, or traceable to, a specified source such as a language, place, or cultural context.
-
D.
speciesOrigin
Indicates the place, environment, or source from which a species originally arose or evolved.
-
E.
languageOfNamesake
Indicates the language in which the namesake of an entity (such as a person, place, or object) is named or expressed.
- 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.