Triple
T104914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mercury (branch) insignia |
E2118
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | U.S. Army insignia |
C3741
|
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. Army insignia Context triple: [Mercury (branch) insignia, instanceOf, U.S. Army insignia]
-
A.
military uniform
A military uniform is a standardized set of clothing and accessories worn by armed forces personnel to signify rank, role, and affiliation while promoting discipline and unity.
-
B.
military camouflage pattern
A military camouflage pattern is a systematically designed arrangement of colors and shapes intended to conceal personnel, vehicles, or equipment by blending them into specific environmental backgrounds and disrupting visual detection.
-
C.
branch of the United States Army
A branch of the United States Army is a specialized functional category, such as Infantry or Signal Corps, that organizes soldiers, training, and equipment around a distinct mission set and expertise area within the Army.
-
D.
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.
-
E.
military organization
A military organization is a structured group of armed forces personnel and resources, organized under a defined hierarchy and command system, to plan, coordinate, and conduct defense and combat operations in support of a state’s strategic objectives.
- 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_69a24e0a5b7c81908d52da08c60dabc4 |
completed | Feb. 28, 2026, 2:08 a.m. |
Created at: Feb. 28, 2026, 2:12 a.m.