Triple
T19807430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Województwo wołyńskie |
E475850
|
entity |
| Predicate | partOfHistoricalRegion |
P13711
|
FINISHED |
| Object | Ruś |
—
|
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: Ruś | Statement: [Województwo wołyńskie, partOfHistoricalRegion, Ruś]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ruś Context triple: [Województwo wołyńskie, partOfHistoricalRegion, Ruś]
-
A.
Rusko
Rusko is a small municipality in southwestern Finland known for its rural character and proximity to the city of Turku.
-
B.
Rusko
Rusko is a British electronic music producer and DJ known for pioneering the modern dubstep sound.
-
C.
Rusa
Rusa is a genus of deer native to South and Southeast Asia, including species such as the Javan rusa and sambar.
-
D.
Rusguniae
Rusguniae was an important ancient coastal city in the Roman province of Mauretania Caesariensis, located in what is now northern Algeria.
-
E.
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.
- 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_69d8e51bc4208190a1c57d8c5d1b15e4 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65428f5c48190be6ae0d6a77675d2 |
completed | April 20, 2026, 4:28 p.m. |
Created at: April 10, 2026, 1:49 p.m.