Triple
T17949683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xuzhou Garrison Command of the National Revolutionary Army |
E448799
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional garrison command |
C25873
|
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: regional garrison command Context triple: [Xuzhou Garrison Command of the National Revolutionary Army, instanceOf, regional garrison command]
-
A.
reconnaissance regiment
A reconnaissance regiment is a military unit specialized in gathering intelligence on enemy forces and terrain, typically using mobility, stealth, and advanced surveillance equipment to support larger formations.
-
B.
SS regiment
An SS regiment is a military unit of the Nazi Schutzstaffel, typically composed of several battalions, that carried out combat operations and often participated in security, occupation, and war crimes during World War II.
-
C.
regional air command
A regional air command is a military organizational unit responsible for planning, directing, and controlling air operations within a specific geographic area.
-
D.
regional land command
chosen
A regional land command is a military organizational structure responsible for planning, directing, and coordinating all land-based operations and forces within a defined geographic area.
-
E.
regional joint task force
A regional joint task force is a collaborative, multi-agency or multi-national organization formed within a specific geographic area to coordinate and execute integrated operations toward shared security, emergency response, or policy objectives.
- 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_69d8b9f8cca8819099836916c56b7c95 |
completed | April 10, 2026, 8:51 a.m. |
Created at: April 10, 2026, 10:21 a.m.