Triple

T26684353
Position Surface form Disambiguated ID Type / Status
Subject Harbor Defenses of San Francisco E672703 entity
Predicate instanceOf P0 FINISHED
Object United States Army harbor defense command C51898 CONCEPT FINISHED

How this triple was built (1 step)

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.

CD Concept disambiguation gpt-5-mini-2025-08-07
Target class: United States Army harbor defense command
Context triple: [Harbor Defenses of San Francisco, instanceOf, United States Army harbor defense command]
  • A. U.S. Army sustainment command
    The U.S. Army Sustainment Command is the organization responsible for providing logistics, supply, maintenance, and distribution support to ensure Army forces are equipped and sustained during training, deployment, and combat operations worldwide.
  • B. National Defense Management Center
    The National Defense Management Center is a centralized command and control facility responsible for coordinating, monitoring, and directing a nation's military and defense operations at the strategic level.
  • C. naval shore establishment
    A naval shore establishment is a land-based facility that supports a navy’s operations, administration, training, logistics, and maintenance away from seagoing vessels.
  • D. Marine Air-Ground Task Force logistics element
    The Marine Air-Ground Task Force logistics element is the component responsible for providing comprehensive combat service support—including supply, maintenance, transportation, health services, and engineering—to sustain the MAGTF’s operations across all domains.
  • E. Marine Corps base
    A Marine Corps base is a military installation that provides facilities, training grounds, housing, and logistical support for United States Marine Corps personnel and operations.
  • F. None of above. chosen

Provenance (1 batch)

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_69eecda13424819092b17942c4edf722 completed April 27, 2026, 2:44 a.m.
Created at: April 27, 2026, 3:22 a.m.