Triple
T4283498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Novgorod |
E97210
|
entity |
| Predicate | historicalRegion |
P915
|
FINISHED |
| Object | Rus' |
E158473
|
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: Rus' | Statement: [Novgorod, historicalRegion, Rus']
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rus' Context triple: [Novgorod, historicalRegion, Rus']
-
A.
Rus'
chosen
Rus' was a medieval East Slavic state that emerged in Eastern Europe and laid the foundations for the later Russian, Ukrainian, and Belarusian nations.
-
B.
Rusko
Rusko is a small municipality in southwestern Finland known for its rural character and proximity to the city of Turku.
-
C.
Rusa
Rusa is a genus of deer native to South and Southeast Asia, including species such as the Javan rusa and sambar.
-
D.
Russas
Russas is a municipality in the northeastern Brazilian state of Ceará, known for its agricultural activities and semi-arid climate.
-
E.
ROSSIYA
ROSSIYA is the radio callsign used by Rossiya Airlines, a major Russian carrier based in Saint Petersburg.
- 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_69b3454595848190a0e6bbb6a2bea040 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3503a84548190989a96d1a30d6ef7 |
completed | March 12, 2026, 11:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b5f5b965c48190990357f4cb4e30cb |
completed | March 14, 2026, 11:56 p.m. |
Created at: March 12, 2026, 11:07 p.m.