Triple
T8465437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Australian Defence Force Cadets |
E200149
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Australian organisation |
C21523
|
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: Australian organisation Context triple: [Australian Defence Force Cadets, instanceOf, Australian organisation]
-
A.
Australian company
An Australian company is a legally registered business entity that operates in or from Australia, subject to Australian corporate, tax, and regulatory frameworks.
-
B.
Australian government agency
An Australian government agency is an official public sector organization established by the Commonwealth or a state/territory government to implement laws, deliver services, and administer specific policy areas within Australia.
-
C.
Australian youth organisation
chosen
An Australian youth organisation is a group that provides programs, support, and opportunities for young people in Australia to develop skills, participate in their communities, and advocate for their interests.
-
D.
Australian government department
An Australian government department is a formal administrative unit of the Australian Public Service responsible for implementing federal laws, policies, and programs within a specific portfolio area under the direction of a minister.
-
E.
Australian person
An Australian person is an individual who is a citizen or resident of Australia, typically associated with its diverse multicultural society, English language use, and cultural practices influenced by Indigenous, British, and broader global traditions.
- 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_69ca83198c4c8190a337bf717d1813f5 |
completed | March 30, 2026, 2:05 p.m. |
Created at: March 30, 2026, 6:11 p.m.