Triple
T16024012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Victoria Barracks, Sydney |
E388672
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Australian Army barracks |
C36856
|
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 Army barracks Context triple: [Victoria Barracks, Sydney, instanceOf, Australian Army barracks]
-
A.
Royal Australian Navy shore establishment
A Royal Australian Navy shore establishment is a land-based facility that supports naval operations through administration, training, logistics, maintenance, and other essential services.
-
B.
British Army facility
A British Army facility is a location owned, operated, or used by the British Army for purposes such as training, administration, logistics, accommodation, storage, or operational deployment.
-
C.
Australian Army formation
An Australian Army formation is a structured military organization composed of multiple units and sub-units, established to plan, coordinate, and conduct land operations under a unified command within the Australian Army.
-
D.
component of the Australian Army
A component of the Australian Army is an organizational subdivision—such as a unit, formation, corps, or support element—that contributes specific capabilities and functions to the Army’s overall mission and operations.
-
E.
Australian Defence Force position
An Australian Defence Force position represents a specific role or appointment within the ADF’s organizational structure, defined by its responsibilities, rank requirements, and placement in the command hierarchy.
- 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_69d86dada3808190825d5f80d72fbe88 |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:55 a.m.