Triple
T13172752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brașov |
E313017
|
entity |
| Predicate | historicalName |
P65
|
FINISHED |
| Object | Kronstadt |
E970261
|
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: [Brașov, historicalName, Kronstadt]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kronstadt Context triple: [Brașov, historicalName, Kronstadt]
-
A.
Kronstadt
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.
Kronstadt
chosen
Kronstadt is a historic Transylvanian city (now known as Brașov, Romania) renowned for its medieval fortifications and Saxon heritage.
-
C.
Severomorsk
Severomorsk is a closed naval town in Russia’s Murmansk Oblast that serves as the main base of the Russian (formerly Soviet) Northern Fleet on the Barents Sea.
-
D.
Sestroretsk
Sestroretsk is a town in northwestern Russia, now part of Saint Petersburg, historically known for its arms factory and seaside resort area on the Gulf of Finland.
-
E.
Sevastopolskaya
Sevastopolskaya is a Moscow Metro station serving the Serpukhovsko–Timiryazevskaya Line in the city’s southern part.
- 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_69d806ac3ee081909b2fd27d060aa974 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98c2f22b881908a0af3af0a0af971 |
completed | April 10, 2026, 11:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6f5e5eacc8190ae39dcdb12c9b563 |
completed | May 3, 2026, 7:14 a.m. |
Created at: April 9, 2026, 9:13 p.m.