Triple

T17909063
Position Surface form Disambiguated ID Type / Status
Subject Diamondhead E447773 entity
Predicate isDurableAgainst P67874 FINISHED
Object Physical attacks 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: Physical attacks | Statement: [Diamondhead, isDurableAgainst, Physical attacks]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isDurableAgainst
Context triple: [Diamondhead, isDurableAgainst, Physical attacks]
  • A. durabilityClass
    Indicates the level or category of resistance an entity has to wear, damage, or degradation over time.
  • B. durabilityModel
    Indicates a relationship where an entity is associated with a specific model or method used to estimate or characterize its durability over time or under certain conditions.
  • C. durabilityCertification
    Indicates that an entity has been formally evaluated and certified to meet specified standards of durability or long-term performance.
  • D. designedToWithstand
    Indicates that something has been intentionally created or engineered to resist, endure, or remain functional under specified conditions, forces, or stresses.
  • E. isResistant chosen
    Indicates that an entity can withstand, oppose, or is not significantly affected by a specified force, influence, or agent.
  • 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_69d8b9f6d394819082a6d69fd1e23d2f completed April 10, 2026, 8:51 a.m.
NER Named-entity recognition batch_69e49e9e4c9881908bfc3a83809d6b85 completed April 19, 2026, 9:21 a.m.
PD Predicate disambiguation batch_69e3d8ec2f6881909d7f54b878cbed37 completed April 18, 2026, 7:18 p.m.
Created at: April 10, 2026, 10:19 a.m.