Triple
T31125561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ROK–US Combined Forces Command Terms of Reference |
E793347
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | foundational command document |
C531
|
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: foundational command document Context triple: [ROK–US Combined Forces Command Terms of Reference, instanceOf, foundational command document]
-
A.
foundational document collection
A foundational document collection is an organized set of core, authoritative records that establish the essential principles, requirements, and context for a system, organization, or project.
-
B.
administrative command
An administrative command is a privileged instruction or operation executed within a system to configure, control, or manage resources, users, and security settings beyond the capabilities of regular users.
-
C.
founding document
chosen
A founding document is an authoritative text that formally establishes an organization, institution, or state by defining its core principles, structure, and governing rules.
-
D.
supporting establishment command
A supporting establishment command is a military or organizational unit responsible for providing logistical, administrative, and operational support to primary mission-focused forces or facilities.
-
E.
strategic document
A strategic document is a formal written plan that outlines an organization’s long-term goals, priorities, and actions for achieving its mission and competitive advantage.
- 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_69f224d1701c819094f429798290e361 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:05 p.m.