Triple
T12054118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Navy–Marine Corps team |
E286995
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | U.S. sea services team |
C30367
|
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: U.S. sea services team Context triple: [United States Navy–Marine Corps team, instanceOf, U.S. sea services team]
-
A.
United States Coast Guard unit
A United States Coast Guard unit is an organized group within the Coast Guard, such as a cutter, station, air station, or specialized team, that performs specific missions related to maritime safety, security, and environmental protection.
-
B.
United Nations team
A United Nations team is a group of international professionals collaboratively working under UN mandates to address global issues such as peace, security, development, and human rights.
-
C.
private military contractor team
A private military contractor team is a coordinated group of hired security and combat specialists who provide military-style services—such as protection, training, and tactical operations—for governments, corporations, or other clients under contractual agreements.
-
D.
U.S. Navy community
A U.S. Navy community is a group of sailors and officers organized around a specific warfare area, specialty, or professional focus, sharing common training, qualifications, and career paths within the Navy.
-
E.
U.S. Navy staff code
A U.S. Navy staff code is a standardized alphanumeric designation that identifies the specific functional area, responsibility, or staff section within a naval command’s organizational structure.
- 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_69d6ab4780948190bdb9f7620c2ac27e |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:47 p.m.