Triple
T8790193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Principality of Ryazan |
E209141
|
entity |
| Predicate | historicalRegion |
P915
|
FINISHED |
| Object | Rus |
E511088
|
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: [Principality of Ryazan, historicalRegion, Rus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rus Context triple: [Principality of Ryazan, historicalRegion, Rus]
-
A.
Rus
chosen
Rus was a medieval East Slavic cultural and political realm that laid the foundations for the modern nations of Russia, Ukraine, and Belarus.
-
B.
Russo
Russo is an Italian surname commonly used as a variant of Rossi, often associated with people of Italian heritage.
-
C.
Russian
Russian is an East Slavic language that serves as the official language of Russia and a major lingua franca across much of Eastern Europe and Central Asia.
-
D.
RUS
RUS is the National Rail station code assigned to Russell Square station in London.
-
E.
RUS
RUS is the three-letter International Olympic Committee country code used to represent Russia in Olympic competitions.
- 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_69ca836168108190bb43d3dc235c1f55 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5f8d25f881908863d636fa57a8a2 |
completed | March 31, 2026, 11:58 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cf5210454c8190aa83d941893a4bc5 |
completed | April 3, 2026, 5:37 a.m. |
Created at: March 30, 2026, 6:43 p.m.