Triple

T1058461
Position Surface form Disambiguated ID Type / Status
Subject Union E22849 entity
Predicate navalStrength P21383 FINISHED
Object maintained naval blockade of Confederate ports 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: maintained naval blockade of Confederate ports | Statement: [Union, navalStrength, maintained naval blockade of Confederate ports]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: navalStrength
Context triple: [Union, navalStrength, maintained naval blockade of Confederate ports]
  • A. navalPowerStatus chosen
    Indicates the relative strength, capability, or strategic standing of an entity’s naval forces compared to others or to defined benchmarks.
  • B. navalFleet
    Indicates a relationship where multiple naval vessels are organized and operate together as a coordinated maritime military force.
  • C. navalForceComposition
    Indicates the makeup and distribution of different types of naval units or vessels within a particular naval force.
  • D. warPower
    Indicates the authority, capability, or legal power to initiate, conduct, or manage acts of war or armed conflict.
  • E. navalAccess
    Indicates that one entity has the right or ability to use another entity’s naval facilities, waters, or maritime routes for military or strategic purposes.
  • 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_69a493dada0481909c43649f9843ea91 completed March 1, 2026, 7:30 p.m.
NER Named-entity recognition batch_69a4ba6e35ac8190802341c31bda0e3b completed March 1, 2026, 10:15 p.m.
PD Predicate disambiguation batch_69a4b7340a048190807363f19d17a58f completed March 1, 2026, 10:01 p.m.
Created at: March 1, 2026, 7:42 p.m.