Triple
T29277616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Police Regional Offices |
E742284
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | major territorial command |
C55159
|
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: major territorial command Context triple: [Police Regional Offices, instanceOf, major territorial command]
-
A.
Major Command Subordinate Unit
A Major Command Subordinate Unit is an organizational entity that operates under a major command, executing its directives and managing assigned missions, resources, and personnel within a defined scope of responsibility.
-
B.
major command echelon
A major command echelon is a high-level organizational tier within a military or large institution that oversees multiple subordinate units and directs strategic operations, resources, and policies across a broad mission area.
-
C.
regional land command
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.
-
D.
Geographic combatant command
A geographic combatant command is a unified military command responsible for planning and conducting operations within a specific, defined region of the world.
-
E.
subordinate unified combatant command
A subordinate unified combatant command is a command established by a unified combatant command to conduct operations on a continuing basis within a specific functional or geographic area under the authority of that parent unified command.
- 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_69f0912124d48190a046642b69407f4c |
completed | April 28, 2026, 10:51 a.m. |
Created at: April 28, 2026, 12:52 p.m.