Triple

T9763813
Position Surface form Disambiguated ID Type / Status
Subject Master Gunnery Sergeant E236732 entity
Predicate introducedAsRank P47925 FINISHED
Object World War II era (as a technical senior enlisted rank) 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: World War II era (as a technical senior enlisted rank) | Statement: [Master Gunnery Sergeant, introducedAsRank, World War II era (as a technical senior enlisted rank)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: introducedAsRank
Context triple: [Master Gunnery Sergeant, introducedAsRank, World War II era (as a technical senior enlisted rank)]
  • A. namedForRank
    Indicates that something is named after a specific rank or title held by an entity.
  • B. representsRank
    Indicates that one entity serves as the rank, status, or hierarchical level assigned to another entity.
  • C. promotedToRankBy
    Indicates that an entity was elevated to a particular rank or position through the action or decision of another entity.
  • D. isRank chosen
    Indicates that one entity serves as the rank, level, or hierarchical position associated with another entity.
  • E. rankedAs
    Indicates that one entity is assigned a specific position or level in an ordered ranking relative to others.
  • 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_69ca84d64f6c8190a4ed4e9f5936eda5 completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cda09ed54c8190a5879e14184cddf4 completed April 1, 2026, 10:47 p.m.
PD Predicate disambiguation batch_69cd03d0772c8190bd1750cf1cfba309 completed April 1, 2026, 11:38 a.m.
Created at: March 30, 2026, 8:25 p.m.