Triple
T1549420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naval Air Systems Command |
E33053
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United States Navy systems command |
C8073
|
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 Navy systems command Context triple: [Naval Air Systems Command, instanceOf, United States Navy systems command]
-
A.
United States Navy position
A United States Navy position is a specific role or billet within the Navy’s organizational structure, defined by its rank, responsibilities, and place in the chain of command.
-
B.
naval administrative office
A naval administrative office is an organizational unit responsible for managing the paperwork, personnel records, logistics, and regulatory compliance that support the operations of a navy or naval installation.
-
C.
naval air service
A naval air service is a military aviation branch responsible for operating aircraft and related support units in direct support of a nation's navy, including maritime patrol, fleet air defense, anti-submarine warfare, and carrier-based operations.
-
D.
United States Navy medical facility
A United States Navy medical facility is a healthcare institution operated by the U.S. Navy that provides medical, dental, and preventive services to active-duty personnel, their families, and eligible beneficiaries in support of naval operations and readiness.
-
E.
naval arsenal
A naval arsenal is a specialized military facility where warships are built, repaired, equipped, and supplied with weapons, ammunition, and other naval stores.
- 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_69a885ee6db8819099502bc5ce8af881 |
completed | March 4, 2026, 7:20 p.m. |
Created at: March 4, 2026, 7:26 p.m.