Triple
T17822499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Volosovsky District |
E445021
|
entity |
| Predicate | containsSettlement |
P847
|
FINISHED |
| Object | Volosovo |
E1289275
|
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: Volosovo | Statement: [Volosovsky District, containsSettlement, Volosovo]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Volosovo Context triple: [Volosovsky District, containsSettlement, Volosovo]
-
A.
Volosovo
chosen
Volosovo is a town in Leningrad Oblast, Russia, serving as a local hub for administration, transport, and services in the surrounding rural area.
-
B.
Volosko
Volosko is a historic coastal village and former fishing port on the Adriatic Sea, now part of the town of Opatija in western Croatia.
-
C.
Lyaskovets
Lyaskovets is a small town in north-central Bulgaria known for its historical monasteries and traditional Bulgarian architecture.
-
D.
Volodarsk
Volodarsk is a town in Nizhny Novgorod Oblast, Russia, known for its location along the Klyazma River and its industrial character.
-
E.
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.
- 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_69d8b9f0de78819099395b14db75a8a6 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e48911b660819097fc7ea94665a02a |
completed | April 19, 2026, 7:49 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0306f1f3908190b51533fb9bc54430 |
completed | May 12, 2026, 10:54 a.m. |
Created at: April 10, 2026, 10:15 a.m.