Triple

T4155892
Position Surface form Disambiguated ID Type / Status
Subject Leatherback E91412 entity
Predicate abilityDetail P8715 FINISHED
Object Can emit an EMP that disables Jaeger systems 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: Can emit an EMP that disables Jaeger systems | Statement: [Leatherback, abilityDetail, Can emit an EMP that disables Jaeger systems]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: abilityDetail
Context triple: [Leatherback, abilityDetail, Can emit an EMP that disables Jaeger systems]
  • A. scopeDetail
    Indicates a more specific or refined characterization of the extent, boundaries, or coverage of something within a broader scope.
  • B. ability chosen
    Indicates that an entity has the capacity or power to perform a particular action or achieve a specific outcome.
  • C. statedReason
    Indicates that one entity expresses or provides another entity as the explanation, justification, or motive for an action, event, or claim.
  • D. protectionReason
    Indicates the justification or cause for which protection is provided or required in the relationship between entities.
  • E. legalDetail
    Indicates that there is specific legal information, conditions, or attributes associated with the related entity or relationship.
  • 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_69aed9626ebc8190a39de631788bea3e completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69af0321eee88190871c1d4bf44a5007 completed March 9, 2026, 5:28 p.m.
PD Predicate disambiguation batch_69af018dc90c8190a754b1bfbc802e80 completed March 9, 2026, 5:21 p.m.
Created at: March 9, 2026, 3:44 p.m.