Triple
T1865700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MEPS |
E34915
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United States military processing facility |
C1086
|
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 military processing facility Context triple: [MEPS, instanceOf, United States military processing facility]
-
A.
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.
-
B.
military installation
chosen
A military installation is a designated facility or area where armed forces are stationed, trained, equipped, and supported to conduct defense and security operations.
-
C.
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.
-
D.
former United States Mint facility
A former United States Mint facility is a decommissioned government building that once produced or processed U.S. coinage and related monetary materials but is no longer in active minting operation.
-
E.
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.
- 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_69a88600b2f88190bc09303e68ab517e |
completed | March 4, 2026, 7:20 p.m. |
Created at: March 4, 2026, 7:34 p.m.