Triple
T30319351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City of Brisbane Squadron |
E771145
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military heritage organisation |
C1368
|
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: military heritage organisation Context triple: [City of Brisbane Squadron, instanceOf, military heritage organisation]
-
A.
military museum
chosen
A military museum is an institution that collects, preserves, and exhibits artifacts, documents, and stories related to armed forces, warfare, and military history for public education and research.
-
B.
heritage conservation organization
A heritage conservation organization is an entity dedicated to identifying, protecting, preserving, and promoting cultural, historical, and natural heritage resources for present and future generations.
-
C.
Scottish heritage society
A Scottish heritage society is an organization dedicated to preserving, promoting, and celebrating Scottish culture, history, traditions, and ancestry among its members and the wider community.
-
D.
commemorative society
A commemorative society is an organized group dedicated to preserving the memory, legacy, and associated traditions of a person, event, place, or cultural heritage through activities such as research, education, and ceremonial observances.
-
E.
cultural heritage organisation
A cultural heritage organisation is an institution dedicated to preserving, managing, and promoting tangible and intangible cultural assets—such as artifacts, traditions, sites, and knowledge—for the benefit of present and future generations.
- 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_69f22489ee8481909344649bfbb92e83 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:52 p.m.