Triple
T28876153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naval Reserve Force |
E732274
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | component of the Royal Thai Navy |
C37133
|
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: component of the Royal Thai Navy Context triple: [Naval Reserve Force, instanceOf, component of the Royal Thai Navy]
-
A.
component of the Royal New Zealand Navy
A component of the Royal New Zealand Navy is any organizational unit, vessel, establishment, or formation that operates under the authority of the RNZN to contribute to New Zealand’s maritime defense and security.
-
B.
specialized unit of the Philippine Navy
A specialized unit of the Philippine Navy is a distinct, mission-focused naval formation equipped with tailored personnel, training, and resources to conduct specific maritime operations such as special warfare, coastal defense, or support functions.
-
C.
branch of the Royal Thai Army
A branch of the Royal Thai Army is a major organizational subdivision responsible for specific military functions, capabilities, and operations within Thailand’s land warfare forces.
-
D.
branch of the Royal Netherlands Navy
A branch of the Royal Netherlands Navy is a distinct organizational component responsible for specific maritime defense, support, or operational functions within the overall naval structure of the Netherlands.
-
E.
component of navy
chosen
A component of navy represents a distinct organizational unit, asset, or capability within a naval force, such as ships, personnel, equipment, or support structures, that contributes to maritime operations and defense.
- 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_69f05b06807c81909b4bbd4c20403a2b |
completed | April 28, 2026, 7 a.m. |
Created at: April 28, 2026, 7:38 a.m.