Triple
T7582998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | naval oceanography command activity |
E179537
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | naval meteorology and oceanography unit |
C20348
|
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: naval meteorology and oceanography unit Context triple: [naval oceanography command activity, instanceOf, naval meteorology and oceanography unit]
-
A.
naval research laboratory
A naval research laboratory is a specialized scientific and engineering institution dedicated to developing, testing, and evaluating technologies and systems to support and advance a nation's maritime and naval capabilities.
-
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 unit
chosen
A naval unit is an organized group of maritime military assets—such as ships, submarines, aircraft, and personnel—structured to conduct operations and missions at sea.
-
D.
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.
-
E.
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.
- F. None of above.
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_69c69f327db881909a21ae3b156f8ded |
completed | March 27, 2026, 3:16 p.m. |
Created at: March 27, 2026, 3:52 p.m.