Triple
T17333148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oreshek Fortress |
E420864
|
entity |
| Predicate | alsoKnownAs |
P39
|
FINISHED |
| Object | Oreshek |
—
|
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: Oreshek | Statement: [Oreshek Fortress, alsoKnownAs, Oreshek]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Oreshek Context triple: [Oreshek Fortress, alsoKnownAs, Oreshek]
-
A.
Oreshek
chosen
Oreshek is the historic Russian fortress on Lake Ladoga that later gave rise to the town of Shlisselburg.
-
B.
Olenka
Olenka is a Slavic diminutive form of the female given name Olga, often used as an affectionate or familiar nickname.
-
C.
Zolotonosha
Zolotonosha is a historic town in central Ukraine, located in the Cherkasy region on the banks of the Zolotonoshka River.
-
D.
Orlovets
Orlovets is a prominent mountain peak in Bulgaria’s Rila Mountains, popular with hikers and climbers for its rugged alpine terrain and scenic views.
-
E.
Maloyaroslavets
Maloyaroslavets is a historic town in western Russia known for the 1812 Battle of Maloyaroslavets during Napoleon’s invasion.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d889d3adc881909319f1edb8d2a956 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a0fa57881909071fd395b3d46c4 |
completed | April 19, 2026, 2:12 a.m. |
Created at: April 10, 2026, 5:43 a.m.