Triple

T8843863
Position Surface form Disambiguated ID Type / Status
Subject Constitution-class frigate E210453 entity
Predicate designedToOutfight P47072 FINISHED
Object other frigates 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: other frigates | Statement: [Constitution-class frigate, designedToOutfight, other frigates]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: designedToOutfight
Context triple: [Constitution-class frigate, designedToOutfight, other frigates]
  • A. designedToDefeat chosen
    Indicates that one entity is intentionally created or configured with the purpose of overcoming, neutralizing, or rendering ineffective another entity.
  • B. fightingOutOf
    Indicates that an individual is competing or representing themselves in a fight or match while being officially associated with a particular location, camp, or organization.
  • C. diesFighting
    Indicates that an entity dies as a direct result of engaging in a fight or combat.
  • D. combatStyleAgainst
    Indicates the specific way or method one entity uses to fight or engage in combat when facing another entity.
  • E. designedToWithstand
    Indicates that something has been intentionally created or engineered to resist, endure, or remain functional under specified conditions, forces, or stresses.
  • 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_69ca838967bc8190b46c3c80a2887ea4 completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc608a73c88190875409fef79ffc8a completed April 1, 2026, 12:02 a.m.
PD Predicate disambiguation batch_69cc5c25b874819084c9ba391703e066 completed March 31, 2026, 11:43 p.m.
Created at: March 30, 2026, 6:48 p.m.