Triple
T24156862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ushba Glacier |
E598705
|
entity |
| Predicate | locatedInPartOfWorld |
P136571
|
FINISHED |
| Object | South Caucasus |
—
|
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: South Caucasus | Statement: [Ushba Glacier, locatedInPartOfWorld, South Caucasus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInPartOfWorld Context triple: [Ushba Glacier, locatedInPartOfWorld, South Caucasus]
-
A.
locatedIn
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
B.
partlyLocatedOn
Indicates that one entity is situated such that only a portion of it lies on or within the spatial extent of another entity.
-
C.
sometimesLocatedIn
Indicates that an entity is located in a given place only at certain times or under certain conditions, rather than permanently or always.
-
D.
locatedInOceania
Indicates that one entity is geographically situated within the region of Oceania.
-
E.
locatedInAsia
chosen
Indicates that the subject entity is geographically situated within the continent of Asia.
- 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_69e288cb0a3081909ef221744f274384 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1e0e5bdb48190aa2d369942b85220 |
completed | April 29, 2026, 10:43 a.m. |
| PD | Predicate disambiguation | batch_69f176585f3481909beb907de252cd98 |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:31 p.m.