Triple
T15116504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arts Projects Australia |
E361052
|
entity |
| Predicate | eventTypeSpecialization |
P37115
|
FINISHED |
| Object | music festivals |
—
|
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: music festivals | Statement: [Arts Projects Australia, eventTypeSpecialization, music festivals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventTypeSpecialization Context triple: [Arts Projects Australia, eventTypeSpecialization, music festivals]
-
A.
eventSpecialty
chosen
Indicates the specific field, theme, or area of focus that an event is primarily concerned with.
-
B.
specialtyEvent
Indicates that an event is designated as a special or distinctive occurrence, often differing from regular or routine events in nature or purpose.
-
C.
specialEventServiceTo
Indicates that a service is specifically provided or designated for a particular special event.
-
D.
eventTypePromoted
Indicates that an event has been elevated in status or visibility, such as being highlighted, featured, or moved to a more prominent position.
-
E.
typeOfEvent
Indicates that one entity is classified as a specific kind or category of event.
- 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_69d85a0491ec8190830960be8fafb994 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0059ca9048190b742e70e818ee64f |
completed | April 15, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69deb96c1d9c81909351558ed97bc5b7 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:05 a.m.