Triple
T1286078
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bethesda Naval Hospital |
E27436
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United States Navy medical facility |
C6922
|
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 medical facility Context triple: [Bethesda Naval Hospital, instanceOf, United States Navy medical facility]
-
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.
United States Army installation
A United States Army installation is a designated military facility, base, or post that supports the housing, training, operations, logistics, and administration of Army personnel and equipment.
-
D.
United States Air Force base
A United States Air Force base is a military installation that supports Air Force operations through facilities for aircraft, personnel, training, logistics, and command and control activities.
-
E.
United States Marine Corps major command
A United States Marine Corps major command is a high-level organizational entity responsible for overseeing, directing, and supporting large-scale Marine Corps forces and operations within a defined functional or geographic area.
- 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_69a496d4ec448190ad653b2590c46711 |
completed | March 1, 2026, 7:43 p.m. |
Created at: March 1, 2026, 7:51 p.m.