Triple
T2686163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kuban River |
E57489
|
entity |
| Predicate | majorCityOnRiver |
P316
|
FINISHED |
| Object | Armavir |
E194054
|
NE 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: Armavir | Statement: [Kuban River, majorCityOnRiver, Armavir]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Armavir Context triple: [Kuban River, majorCityOnRiver, Armavir]
-
A.
Armavir
chosen
Armavir is a city in southwestern Russia known as an industrial and transportation center on the Kuban River.
-
B.
Armavir Province
Armavir Province is a region in western Armenia known as a historical and religious center, notably home to the spiritual heart of the Armenian Apostolic Church.
-
C.
Kislovodsk
Kislovodsk is a Russian spa and resort city in the North Caucasus, renowned for its mineral springs and mountainous surroundings.
-
D.
Gelendzhik
Gelendzhik is a Black Sea resort city in southern Russia known for its beaches, scenic bay, and tourism infrastructure.
-
E.
Tuapse
Tuapse is a Black Sea port town in southern Russia known as a seaside resort and industrial center within Krasnodar Krai.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ab4a5028388190a36f3baf1588309e |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd9ef2fe0819082bbe746ca682a7e |
completed | March 7, 2026, 7:55 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69afa07228088190bb4942b3a25c938b |
completed | March 10, 2026, 4:39 a.m. |
Created at: March 6, 2026, 9:54 p.m.