Triple
T19011911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Navy Section |
E465249
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | naval cadet organisation component |
C21522
|
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: naval cadet organisation component Context triple: [Royal Navy Section, instanceOf, naval cadet organisation component]
-
A.
naval cadet organisation
chosen
A naval cadet organisation is a structured youth program that provides maritime-themed training, discipline, and leadership development to prepare young people for potential careers or roles in naval and maritime services.
-
B.
naval administrative office
A naval administrative office is an organizational unit responsible for managing the paperwork, personnel records, logistics, and regulatory compliance that support the operations of a navy or naval installation.
-
C.
cadet organisation
A cadet organisation is a structured youth program, often affiliated with military or uniformed services, that develops leadership, discipline, and practical skills through training, activities, and community engagement.
-
D.
naval office
A naval office is an administrative entity within a navy responsible for managing operations, logistics, personnel, and documentation related to maritime military activities.
-
E.
naval design organization
A naval design organization is an entity responsible for conceiving, developing, and integrating the technical, structural, and systems designs of naval vessels to meet specified operational, safety, and regulatory requirements.
- 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_69d8dd025c188190a1d81f5b4ec7e2c6 |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 10, 2026, 12:02 p.m.