Triple
T36567557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Koori |
E902018
|
entity |
| Predicate | usedInEducationContext |
P45097
|
FINISHED |
| Object | Koori education programs in Victoria |
—
|
LITERAL 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 education programs in Victoria | Statement: [Koori, usedInEducationContext, Koori education programs in Victoria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInEducationContext Context triple: [Koori, usedInEducationContext, Koori education programs in Victoria]
-
A.
usedInEducationIn
Indicates that something is employed or applied within educational contexts in a particular place or institution.
-
B.
usesForEducationAdministration
Indicates that something is used for managing or supporting educational administration activities or processes.
-
C.
educationalContext
Indicates the situational or institutional setting in which an educational activity, interaction, or resource takes place.
-
D.
educationUse
chosen
Indicates the use or application of something specifically for educational purposes or in an educational context.
-
E.
hasEducationalUse
Indicates that something is intended to be used for educational or instructional purposes.
- F. None of above.
Provenance (3 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_69f76e6416708190a9754b8c52d4e453 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff14d596e88190be5263b7f96a96cd |
completed | May 9, 2026, 11:04 a.m. |
| PD | Predicate disambiguation | batch_69ff13f0208081909369aeb3b77a6b1f |
completed | May 9, 2026, 11:01 a.m. |
Created at: May 3, 2026, 4:11 p.m.