Triple

T36525484
Position Surface form Disambiguated ID Type / Status
Subject Koori Court E900289 entity
Predicate involves P1256 FINISHED
Object Koori Court Officer
A Koori Court Officer is a specialist court staff member who supports Aboriginal and Torres Strait Islander participants in Koori Court proceedings, helping to coordinate services and ensure culturally appropriate processes.
E900289 NE FINISHED

How this triple was built (2 steps)

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.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Koori Court Officer | Statement: [Koori Court, involves, Koori Court Officer]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Koori Court Officer
Triple: [Koori Court, involves, Koori Court Officer]
Generated description
A Koori Court Officer is a specialist court staff member who supports Aboriginal and Torres Strait Islander participants in Koori Court proceedings, helping to coordinate services and ensure culturally appropriate processes.

Provenance (5 batches)

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_69f76e5eedb88190a393b8c623f71dd7 completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69f7c2173c048190932d09459b238390 completed May 3, 2026, 9:45 p.m.
NED1 Entity disambiguation (via context triple) batch_6a39dbe38b6881908ec63b48b4f147c1 completed June 23, 2026, 1:05 a.m.
NEDg Description generation batch_6a39de5bb93481909ee74b44eb857a2d completed June 23, 2026, 1:16 a.m.
NED2 Entity disambiguation (via description) batch_6a39df8d99648190afa15118801b0db1 completed June 23, 2026, 1:21 a.m.
Created at: May 3, 2026, 4:11 p.m.