Triple
T7549903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beloselsky-Belozersky family |
E178503
|
entity |
| Predicate | hasAncestralOrigin |
P194
|
FINISHED |
| Object | Belozersk |
E364924
|
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: Belozersk | Statement: [Beloselsky-Belozersky family, hasAncestralOrigin, Belozersk]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Belozersk Context triple: [Beloselsky-Belozersky family, hasAncestralOrigin, Belozersk]
-
A.
Belozersk
chosen
Belozersk is a historic town in northwestern Russia known for its medieval heritage and location near Lake Beloye.
-
B.
Borovsk
Borovsk is a historic town in western Russia known for its well-preserved architecture, monasteries, and role in regional trade and culture.
-
C.
Kozelsk
Kozelsk is a historic town in western Russia known for its medieval defenses and location within Kaluga Oblast.
-
D.
Ostashkov
Ostashkov is a historic town in western Russia situated on the shores of Lake Seliger, known as a local tourist and pilgrimage center.
-
E.
Mozhaisk
Mozhaisk is a historic town in Moscow Oblast, Russia, known for its strategic military importance as a western defensive outpost for Moscow and its notable architectural and cultural heritage.
- 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_69c69f2cbe08819088f9eb0c03ef529b |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f8b35ba481908e1e5bbf329daa33 |
completed | March 27, 2026, 9:37 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c8ac86982c8190a808ba1b98314829 |
completed | March 29, 2026, 4:37 a.m. |
Created at: March 27, 2026, 3:49 p.m.