Triple
T33557787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Earth Army |
E859529
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fictional United States Army unit |
C65149
|
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: fictional United States Army unit Context triple: [New Earth Army, instanceOf, fictional United States Army unit]
-
A.
U.S. Army Ranger unit
A U.S. Army Ranger unit is an elite, highly trained light infantry force specializing in rapid deployment, direct action raids, special reconnaissance, and other high-risk missions in support of U.S. military objectives.
-
B.
U.S. Army regiment
A U.S. Army regiment is a traditional military unit designation that historically grouped multiple battalions or companies under a common lineage and identity, now used primarily for organizational, administrative, and ceremonial purposes rather than as a primary tactical formation.
-
C.
New York Army National Guard unit
A New York Army National Guard unit is a state-based military organization composed of part-time soldiers who train regularly and can be mobilized for both state emergencies and federal missions.
-
D.
U.S. Army medical unit
A U.S. Army medical unit is a military organization that provides coordinated medical care, treatment, evacuation, and health support to soldiers and authorized personnel in both garrison and deployed operational environments.
-
E.
U.S. Army task force
A U.S. Army task force is a temporary, mission-tailored organization composed of units from different branches and echelons, formed to accomplish a specific operational objective.
- 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_69f3497b2b68819093207971b5e13dc8 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:40 a.m.