Triple
T4826634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Georgievsk |
E107840
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Georgievsk |
E471019
|
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: Georgievsk | Statement: [Treaty of Georgievsk, locatedIn, Georgievsk]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Georgievsk Context triple: [Treaty of Georgievsk, locatedIn, Georgievsk]
-
A.
Georgievsk
chosen
Georgievsk is a town in Russia’s Stavropol Krai, historically notable as the site where the 1783 Treaty of Georgievsk between the Russian Empire and the Kingdom of Kartli-Kakheti was signed.
-
B.
Samokov
Samokov is a Bulgarian town in the Rila Mountains known historically for its ironworking and as a gateway to nearby ski and hiking areas.
-
C.
Krasnov
Krasnov is a Russian surname borne by various notable figures in military, political, and cultural history.
-
D.
Jurjev
Jurjev is a historical name for the Estonian city of Tartu, reflecting its past under various regional powers.
-
E.
Kuzminki
Kuzminki is a Moscow Metro station on the Tagansko–Krasnopresnenskaya Line serving the Kuzminki District in southeastern Moscow.
- 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_69bd43fac8188190803f0327190621e4 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6caf22308190a2048ec6acfa5af2 |
completed | March 20, 2026, 3:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be5cb748d081908fc32b2cea994b35 |
completed | March 21, 2026, 8:54 a.m. |
Created at: March 20, 2026, 1:24 p.m.