Triple

T18150595
Position Surface form Disambiguated ID Type / Status
Subject Revelation of the Daleks E434489 entity
Predicate featuresCharacter P626 FINISHED
Object Grigory 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: Grigory | Statement: [Revelation of the Daleks, featuresCharacter, Grigory]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Grigory
Context triple: [Revelation of the Daleks, featuresCharacter, Grigory]
  • A. Grigory chosen
    Grigory is a masculine given name of Russian origin, historically borne by notable figures such as statesman and nobleman Grigory Orlov.
  • B. Grigory Rapota
    Grigory Rapota is a Russian statesman and diplomat who has held several high-ranking government posts, including serving as a presidential plenipotentiary envoy.
  • C. Grigory Spiridov
    Grigory Spiridov was a prominent 18th-century Russian admiral best known for his leadership in the Russo-Turkish War, particularly at the Battle of Chesma.
  • D. Gavril
    Gavril is a masculine given name, commonly used in Slavic and Eastern European cultures, that derives from the Hebrew name Gabriel.
  • E. Vasily
    Vasily is a masculine given name of Slavic origin, commonly used in Russian-speaking countries.
  • 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_69d8b90aac308190801e2c57d8c5bfe5 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4de3812e8819097f025476d5c6a1d completed April 19, 2026, 1:52 p.m.
Created at: April 10, 2026, 10:29 a.m.