Triple

T27363899
Position Surface form Disambiguated ID Type / Status
Subject Wildcat Division E685902 entity
Predicate hasShoulderSleeveInsigniaShape P99173 FINISHED
Object circular design featuring a wildcat 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: circular design featuring a wildcat | Statement: [Wildcat Division, hasShoulderSleeveInsigniaShape, circular design featuring a wildcat]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasShoulderSleeveInsigniaShape
Context triple: [Wildcat Division, hasShoulderSleeveInsigniaShape, circular design featuring a wildcat]
  • A. hasShoulderPatchShape chosen
    Indicates that one entity possesses a shoulder patch whose form or outline matches the specified shape.
  • B. hasShoulderButtons
    Indicates that an object, typically a device or controller, includes buttons positioned on its shoulders or top side edges.
  • C. hasHeraldicShieldShape
    Indicates that an entity’s heraldic shield is characterized by a specific geometric or stylistic shape.
  • D. hasTypeOfInsignia
    Indicates that an entity bears or is associated with a specific kind or category of insignia.
  • E. wearsInsigniaAt
    Indicates that an entity is wearing or displaying a particular insignia at a specified location or point in time.
  • 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_69ef14887c288190931b8431fdbf53c4 completed April 27, 2026, 7:47 a.m.
NER Named-entity recognition batch_69f674e06c9481909ed0ea736408f0d7 completed May 2, 2026, 10:04 p.m.
PD Predicate disambiguation batch_69f673c2f81c8190bf369226306eef09 completed May 2, 2026, 9:59 p.m.
Created at: April 27, 2026, 11:55 a.m.