Triple
T30311951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jacaranda Festival |
E770947
|
entity |
| Predicate | oneOfOldestFlowerFestivalsInAustralia |
P170449
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Jacaranda Festival, oneOfOldestFlowerFestivalsInAustralia, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oneOfOldestFlowerFestivalsInAustralia Context triple: [Jacaranda Festival, oneOfOldestFlowerFestivalsInAustralia, true]
-
A.
commencementInAustralia
Indicates that the commencement or starting point of an event, activity, or legal effect occurs within the territory of Australia.
-
B.
festivalFoundedIn
Indicates that a festival was established or created in a specific year or time period.
-
C.
hasRegionalFlower
Indicates that a region is associated with a specific flower designated as its symbolic or representative flower.
-
D.
festivalHeldIn
Indicates that a festival takes place or is hosted at a specific location or venue.
-
E.
festivalObserved
Indicates that a particular festival is celebrated, observed, or commemorated by an entity (such as a person, group, or community).
- F. None of above. chosen
Provenance (4 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_69f22488f224819081b0f3ec41ab975c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f69063edbc81909e7735954aabee0b |
completed | May 3, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_69f68b7b03488190b1db5fde4c7dd6e5 |
completed | May 2, 2026, 11:40 p.m. |
| PDg | Predicate description generation | batch_69f68f6584a88190a8c4d95c0c84bee9 |
completed | May 2, 2026, 11:57 p.m. |
Created at: April 29, 2026, 7:50 p.m.