Triple

T37729897
Position Surface form Disambiguated ID Type / Status
Subject Weapon Ten E940126 entity
Predicate isCodenamedFor P32834 FINISHED
Object tenth iteration of Weapon Plus 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: tenth iteration of Weapon Plus | Statement: [Weapon Ten, isCodenamedFor, tenth iteration of Weapon Plus]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isCodenamedFor
Context triple: [Weapon Ten, isCodenamedFor, tenth iteration of Weapon Plus]
  • A. hasCodenameLanguage
    Indicates that a codename is expressed or defined in a particular language.
  • B. relatedCodename chosen
    Indicates that one entity has an associated or connected codename that is contextually related to it.
  • C. endUseAsCodename
    Indicates that an entity stops being used as a codename for another entity or concept.
  • D. usesCodeName
    Indicates that one entity refers to another entity by a code name or alias instead of its real or full designation.
  • E. servesCodename
    Indicates that one entity provides or uses another entity under a specific codename or alias.
  • 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_69f76edefd048190a32212c5c3919531 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fbaef0cec881908c2742d77d145901 completed May 6, 2026, 9:13 p.m.
PD Predicate disambiguation batch_69fbadf632ec8190b14991c971258307 completed May 6, 2026, 9:09 p.m.
Created at: May 3, 2026, 4:18 p.m.