Triple

T8136775
Position Surface form Disambiguated ID Type / Status
Subject Sudebnik of 1497 E189991 entity
Predicate jurisdiction P82 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: [Sudebnik of 1497, jurisdiction, Muscovy]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Muscovy
Context triple: [Sudebnik of 1497, jurisdiction, 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. Mahuva
    Mahuva is a coastal town in Gujarat, India, known for its onion production, coconut plantations, and scenic beaches along the Arabian Sea.
  • C. Pekela
    Pekela is a municipality in the province of Groningen in the northeastern Netherlands, known for its rural character and historical peat colonies.
  • D. 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.
  • E. Isella
    Isella is a small hamlet of the alpine municipality of Macugnaga in northern Italy.
  • 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_69ca82bd9900819099477cdc2eb4244f completed March 30, 2026, 2:03 p.m.
NER Named-entity recognition batch_69cb440171d48190afa4a312ab19389c completed March 31, 2026, 3:48 a.m.
NED1 Entity disambiguation (via context triple) batch_69cc949d9c7c81908efb4880f9250166 completed April 1, 2026, 3:44 a.m.
Created at: March 30, 2026, 5:35 p.m.