Triple
T1640405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tsardom of Russia |
E35455
|
entity |
| Predicate | coreTerritory |
P1103
|
FINISHED |
| Object | Muscovy |
E36313
|
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: Muscovy | Statement: [Tsardom of Russia, coreTerritory, Muscovy]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Muscovy Context triple: [Tsardom of Russia, coreTerritory, Muscovy]
-
A.
Muscovy
chosen
Muscovy was a late medieval and early modern Russian principality centered on Moscow that expanded to form the core of the Russian state.
-
B.
Pekela
Pekela is a municipality in the province of Groningen in the northeastern Netherlands, known for its rural character and historical peat colonies.
-
C.
Pike
Pike is an English surname of Old English origin, often associated with people who lived near a pointed hill or carried a pike as a weapon.
-
D.
Rana
Rana was the hereditary royal title borne by the ruling dynasty of the former princely state of Porbandar in western India.
-
E.
Beaver
Beaver was one of the British ships in Boston Harbor whose tea cargo was destroyed during the Boston Tea Party protest in 1773.
- 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_69a88604618c81908b41f6429c431eb6 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a90a3c883c8190bec1d87ecedf2575 |
completed | March 5, 2026, 4:44 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad609cf8488190ba334bdff2c5e78d |
completed | March 8, 2026, 11:42 a.m. |
Created at: March 4, 2026, 7:28 p.m.