Triple
T14330789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Navy rank system |
E355340
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | hierarchical organization system |
C16104
|
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: hierarchical organization system Context triple: [Royal Navy rank system, instanceOf, hierarchical organization system]
-
A.
management system structure
chosen
A management system structure is the organized framework of roles, processes, and relationships that coordinate resources and activities to achieve an organization’s objectives efficiently and consistently.
-
B.
cumulative hierarchy
The cumulative hierarchy is a conceptual model of the set-theoretic universe built in transfinite stages, where each level consists of all sets that can be formed from the sets at earlier levels.
-
C.
subordinate organization
A subordinate organization is an entity that operates under the authority, control, or oversight of a higher-level organization, carrying out specific functions or responsibilities delegated to it.
-
D.
hierarchical competition structure
A hierarchical competition structure is an organized system in which competitors are arranged in ranked levels or tiers, with advancement or status determined by performance against others within and across these levels.
-
E.
mathematical organization
A mathematical organization is a structured entity—such as a society, institute, or association—dedicated to advancing the study, communication, and application of mathematics through research, education, and collaboration.
- 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_69d8278fa2108190bc0d0e7939c1eb03 |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:13 a.m.