Triple

T18087470
Position Surface form Disambiguated ID Type / Status
Subject Pensacola class E432872 entity
Predicate armamentPhilosophy P128334 FINISHED
Object gun-heavy at expense of protection 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: gun-heavy at expense of protection | Statement: [Pensacola class, armamentPhilosophy, gun-heavy at expense of protection]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: armamentPhilosophy
Context triple: [Pensacola class, armamentPhilosophy, gun-heavy at expense of protection]
  • A. armamentCategory
    Indicates the classification of a weapon or military equipment according to its type or role in armament systems.
  • B. plannedArmament
    Indicates that an entity has a specific weapon or set of weapons intended or scheduled to be equipped or deployed in the future.
  • C. militaryDoctrine
    Indicates that one entity embodies, follows, or defines the strategic military principles, tactics, and operational guidelines used by another entity.
  • D. combatPhilosophy chosen
    Indicates a relationship where an entity’s approach to combat is guided by a particular set of principles, strategies, or ethical beliefs.
  • E. armamentWartime
    Indicates a relationship where an entity serves as a weapon or military equipment used by another entity specifically in a wartime context.
  • 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_69d8b907d05c819083cc3bd6021089e6 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4dd16234c8190b547e893a829d6c5 completed April 19, 2026, 1:48 p.m.
PD Predicate disambiguation batch_69e4330e1f2881908b2506d47c48736b completed April 19, 2026, 1:42 a.m.
Created at: April 10, 2026, 10:27 a.m.