Triple

T31746365
Position Surface form Disambiguated ID Type / Status
Subject VICTORIA REGINA ET IMPERATRIX E810279 entity
Predicate usedInImperialIndiaContext P194998 FINISHED
Object yes LITERAL 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: yes | Statement: [VICTORIA REGINA ET IMPERATRIX, usedInImperialIndiaContext, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usedInImperialIndiaContext
Context triple: [VICTORIA REGINA ET IMPERATRIX, usedInImperialIndiaContext, yes]
  • A. usedImperialStyle
    Indicates that one entity employed or followed the imperial style associated with another entity (such as an era, regime, or authority).
  • B. usedInImperialRussianMaps
    Indicates that something appears or is employed as a feature, label, or reference within maps produced in Imperial Russia.
  • C. capitalDuringBritishRule
    Indicates that a place served as the capital of a region or polity specifically during the period of British rule.
  • D. precedenceInImperialSystem
    Indicates that one entity holds a higher rank, priority, or order than another within an imperial (empire-based) hierarchical system.
  • E. stateDuringBritishRule
    Indicates that the entity was a state or political unit that existed or held that status during the period of British colonial rule.
  • F. None of above. chosen

Provenance (4 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_69f348e233cc819083b6695f70cd75d8 completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69fd974d75e08190af46b1d608769f3b completed May 8, 2026, 7:57 a.m.
PD Predicate disambiguation batch_69fd94ff792c8190bedf4a639d3da809 completed May 8, 2026, 7:47 a.m.
PDg Predicate description generation batch_69fd974c0e8481909fdd312897c647b3 completed May 8, 2026, 7:57 a.m.
Created at: April 30, 2026, 11:26 p.m.