Triple

T21747658
Position Surface form Disambiguated ID Type / Status
Subject Budweiser (U.S. Navy SEAL insignia) E536828 entity
Predicate wearerRankRange P145214 FINISHED
Object enlisted personnel 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: enlisted personnel | Statement: [Budweiser (U.S. Navy SEAL insignia), wearerRankRange, enlisted personnel]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: wearerRankRange
Context triple: [Budweiser (U.S. Navy SEAL insignia), wearerRankRange, enlisted personnel]
  • A. wearerRankCategory
    Indicates the classification of the wearer's rank into a broader rank category (e.g., junior, senior, officer, etc.) within a ranking system.
  • B. wearerType
    Indicates the type or category of entity that is intended to wear or use the associated item.
  • C. wearerMust
    Indicates that a specified item or object is required to be worn by a particular entity under certain conditions or rules.
  • D. wearerStatus
    Indicates the condition or role of an entity in its capacity as a wearer of something (e.g., clothing, equipment, or an accessory).
  • E. wearerEntitlement
    Indicates that an entity has the right or authorization to wear a particular item (such as clothing, equipment, or an accessory).
  • 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_69e0c46eab808190b848242d63a17c47 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69f01a77e19c81909bf26f96aa41a7ce completed April 28, 2026, 2:24 a.m.
PD Predicate disambiguation batch_69e6969c16fc8190b5126c169317d85d completed April 20, 2026, 9:11 p.m.
PDg Predicate description generation batch_69e69f3ed4408190a4a78410bf660c44 completed April 20, 2026, 9:48 p.m.
Created at: April 16, 2026, 6:50 p.m.