Triple
T24041456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bistritsa Glacier |
E595388
|
entity |
| Predicate | countryNamingAuthority |
P154637
|
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: [Bistritsa Glacier, countryNamingAuthority, Bulgaria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryNamingAuthority Context triple: [Bistritsa Glacier, countryNamingAuthority, Bulgaria]
-
A.
institutionNativeName
Indicates that an institution is associated with its official or commonly used name in the institution’s original or local language.
-
B.
administrativeDivisionOfDemonym
Indicates that a term is the demonym (name for residents) associated with a particular administrative division (such as a state, province, or region).
-
C.
onomasticType
Indicates the specific kind or category of a name (e.g., personal, place, or other name type) that characterizes the naming relationship.
-
D.
countrySpecificName
Indicates that an entity has a name or label that is specific to, or used within, a particular country.
-
E.
regionNamedAfter
Indicates that a geographic region derives its name from a specific person, place, event, or other entity.
- F. None of above. chosen
Provenance (4 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_69e288c06a908190899cad4531f32c9a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d8da38548190b2cc04ce7960ef9c |
completed | April 29, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69f1764345388190a3102b62ddb729b4 |
completed | April 29, 2026, 3:08 a.m. |
| PDg | Predicate description generation | batch_69f1785afe3c81909be28986ffe944bf |
completed | April 29, 2026, 3:17 a.m. |
Created at: April 17, 2026, 9:57 p.m.