Triple
T196092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Army Cyber Command |
E3822
|
entity |
| Predicate | operationalDomain |
P794
|
FINISHED |
| Object | cyberspace |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: cyberspace | Statement: [United States Army Cyber Command, operationalDomain, cyberspace]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operationalDomain Context triple: [United States Army Cyber Command, operationalDomain, cyberspace]
-
A.
regulatoryDomain
Indicates that one entity defines or governs the rules, policies, or constraints under which another entity must operate.
-
B.
operatesWithin
chosen
Indicates that one entity carries out its activities, functions, or operations inside the scope, boundaries, or jurisdiction defined by another entity.
-
C.
operationalLayer
Indicates that one entity functions as an operational layer or level through which another entity’s activities, processes, or services are executed or managed.
-
D.
operatesOver
Indicates that one entity performs actions or exerts functional control across, upon, or throughout another entity or domain.
-
E.
operatedAs
Indicates that an entity functioned or was used in the capacity, role, or identity of another entity for some period of time.
- F. None of above.
Provenance (3 batches)
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_69a2548debd48190ae3a06d6e65b53c6 |
completed | Feb. 28, 2026, 2:35 a.m. |
| NER | Named-entity recognition | batch_69a25983b49c819080f7e161904c53da |
completed | Feb. 28, 2026, 2:57 a.m. |
| PD | Predicate disambiguation | batch_69a25677da14819094cd02868fd30c83 |
completed | Feb. 28, 2026, 2:44 a.m. |
Created at: Feb. 28, 2026, 2:41 a.m.