Triple

T5676403
Position Surface form Disambiguated ID Type / Status
Subject Ratatat E125094 entity
Predicate collaboratedWith P435 FINISHED
Object Despot E36813 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: Despot | Statement: [Ratatat, collaboratedWith, Despot]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Despot
Context triple: [Ratatat, collaboratedWith, Despot]
  • A. Domnitor
    Domnitor was the title used in the 19th century for the ruling prince of the united Romanian principalities before the establishment of the kingdom.
  • B. Autokrator
    Autokrator is a Greek imperial title historically used to denote a supreme, absolute ruler, most prominently the Byzantine emperor.
  • C. Basileus
    Basileus is the Greek term for a king or emperor, historically used as the title of sovereign rulers in ancient Greece and later the Byzantine Empire.
  • D. Despot of the Morea chosen
    The Despot of the Morea was a late Byzantine provincial ruler governing the Peloponnese region (Morea) as an appanage of the imperial family.
  • E. Tsar
    A tsar was the title used by Slavic monarchs, most notably the emperors of Russia and earlier rulers of Bulgaria and Serbia, signifying a sovereign equivalent to an emperor.
  • 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_69c008295c808190acfe78915e7d656a completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c023728f488190a3622844d78caa13 completed March 22, 2026, 5:14 p.m.
NED1 Entity disambiguation (via context triple) batch_69c04dbbbe9081908d1915b898722c18 completed March 22, 2026, 8:14 p.m.
Created at: March 22, 2026, 3:43 p.m.