Triple
T27002458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commander of the Army Strategic Reserve Command |
E680148
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Indonesian Army position |
C52364
|
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: Indonesian Army position Context triple: [Commander of the Army Strategic Reserve Command, instanceOf, Indonesian Army position]
-
A.
Imperial Japanese Army position
An Imperial Japanese Army position is a specific military role or rank within the land forces of the Empire of Japan, defining an individual's authority, responsibilities, and place in the army hierarchy.
-
B.
Indian Army position
An Indian Army position is a specific rank or role within the organizational hierarchy of the Indian Army, defining an individual's authority, responsibilities, and duties in military operations and administration.
-
C.
Indonesian youth militias
Indonesian youth militias are organized groups of young people, often mobilized by political, military, or social actors, that engage in paramilitary, security, or protest activities to influence local or national power dynamics.
-
D.
Polish military position
A Polish military position is an organized role or rank within Poland's armed forces, defined by specific duties, authority, and responsibilities in the national defense structure.
-
E.
Javanese military campaign
A Javanese military campaign is a coordinated series of armed operations conducted by Javanese polities or forces to achieve specific political, territorial, or 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_69eeeb52908c8190bd246244686aa455 |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 27, 2026, 6:58 a.m.