Triple
T7777382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | N2/N6 Information Warfare |
E221426
|
entity |
| Predicate | serviceBranchLevel |
P78938
|
FINISHED |
| Object | headquarters level |
—
|
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: headquarters level | Statement: [N2/N6 Information Warfare, serviceBranchLevel, headquarters level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceBranchLevel Context triple: [N2/N6 Information Warfare, serviceBranchLevel, headquarters level]
-
A.
serviceBranch
Indicates the military or organizational branch in which an entity serves or is affiliated.
-
B.
serviceBranchSpecific
Indicates that something is restricted or tailored to a particular branch of service rather than being common across all branches.
-
C.
servesBranch
Indicates that one entity provides services or support to a particular branch or subdivision of an organization.
-
D.
branchOfServiceModelledOn
Indicates that one branch of service is modeled, structured, or designed based on another branch of service.
-
E.
serviceBranchCreationContext
Indicates the organizational or situational context within which a service branch is initially established or created.
- F. None of above. chosen
Provenance (4 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_69ca83ebbef881909ac47f789145fef7 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cae7e779ec8190b77296d9c2ac3210 |
completed | March 30, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69caa488532c819093ac40bba0b3c7ef |
completed | March 30, 2026, 4:27 p.m. |
| PDg | Predicate description generation | batch_69cae7e47c5c8190bca90d45b3cdc25e |
completed | March 30, 2026, 9:15 p.m. |
Created at: March 30, 2026, 4:14 p.m.