Triple

T26522557
Position Surface form Disambiguated ID Type / Status
Subject Supreme Ruler of Russia E669996 entity
Predicate associatedWithMilitaryRank P342 FINISHED
Object Admiral 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: Admiral | Statement: [Supreme Ruler of Russia, associatedWithMilitaryRank, Admiral]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: associatedWithMilitaryRank
Context triple: [Supreme Ruler of Russia, associatedWithMilitaryRank, Admiral]
  • A. usesMilitaryRanks
    Indicates that a system, organization, or context employs formal military rank titles to define roles, hierarchy, or status among its members.
  • B. militaryRankScope
    Indicates the hierarchical level or range of authority that a military rank applies to within an organizational or operational context.
  • C. militaryRank chosen
    Indicates that one entity holds a specific position or level within a hierarchical military ranking system relative to another entity.
  • D. isMilitaryRank
    Indicates that one entity holds a specific position or level within a formal military hierarchy in relation to another.
  • E. militaryRankEligibility
    Indicates that one entity is qualified or permitted to hold, attain, or be considered for a specified military rank.
  • F. None of above.

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_69eeb31b6dcc8190b30632dc3928a0c0 completed April 27, 2026, 12:51 a.m.
NER Named-entity recognition batch_69ff3b32ee148190a3ba3b7600943fef completed May 9, 2026, 1:48 p.m.
PD Predicate disambiguation batch_69ff3a238af88190a2c2245e30299e48 completed May 9, 2026, 1:44 p.m.
Created at: April 27, 2026, 1:29 a.m.