Triple
T6851257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deadly Funny |
E158021
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Indigenous Australian cultural event |
C2709
|
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: Indigenous Australian cultural event Context triple: [Deadly Funny, instanceOf, Indigenous Australian cultural event]
-
A.
Aboriginal Australian
An Aboriginal Australian is a member of the Indigenous peoples of the Australian continent, belonging to diverse cultural and linguistic groups with deep ancestral connections to the land and rich traditions spanning tens of thousands of years.
-
B.
Native American ceremony
A Native American ceremony is a culturally significant ritual or gathering that expresses spiritual beliefs, honors ancestors and the natural world, and strengthens community bonds through traditional practices, songs, dances, and offerings.
-
C.
Australian culture
Australian culture is a diverse blend of Indigenous heritage, British colonial roots, and multicultural influences, characterized by a relaxed lifestyle, egalitarian values, and a strong connection to the outdoors and sport.
-
D.
Indigenous people of Queensland
Indigenous people of Queensland are the Aboriginal and Torres Strait Islander communities whose diverse cultures, languages, and traditions are rooted in the lands and waters of what is now the Australian state of Queensland.
-
E.
cultural event
chosen
A cultural event is a planned gathering or activity that showcases, celebrates, or transmits the traditions, arts, values, or practices of a particular community or society.
- 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_69c6882fae988190864cbba788c5ebb4 |
completed | March 27, 2026, 1:37 p.m. |
Created at: March 27, 2026, 2:20 p.m.