Triple
T514378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kronstadt rebellion |
E10673
|
entity |
| Predicate | place |
P373
|
FINISHED |
| Object | Kronstadt |
E42812
|
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: Kronstadt | Statement: [Kronstadt rebellion, place, Kronstadt]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kronstadt Context triple: [Kronstadt rebellion, place, Kronstadt]
-
A.
Kronstadt
chosen
Kronstadt is a historic Russian naval port and fortress city located on Kotlin Island near Saint Petersburg, long serving as a key base for the Russian Baltic Fleet.
-
B.
Sevastopol
Sevastopol is a major port city on the Black Sea, historically significant as a naval base and the site of key military conflicts.
-
C.
Yalta Sea Port
Yalta Sea Port is a major maritime harbor and transportation hub serving the resort city of Yalta on the southern coast of the Crimean Peninsula.
-
D.
Shlisselburg
Shlisselburg is a historic Russian town near Saint Petersburg, best known for its strategic fortress and former political prison on Lake Ladoga.
-
E.
Nakhodka
Nakhodka is a key port city on Russia’s Pacific coast, serving as an important hub for maritime trade and transport in the Russian Far East.
- 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_69a2e84a0d08819087e01863fcd9abf1 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f1824a248190808591ab3ece7dff |
completed | Feb. 28, 2026, 1:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a4c02c26808190b3078fb04f34572c |
completed | March 1, 2026, 10:39 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.