Triple
T36808653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tyagarah Tea Tree Farm |
E909527
|
entity |
| Predicate | notableEventGenre |
P119424
|
FINISHED |
| Object | blues music |
—
|
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: blues music | Statement: [Tyagarah Tea Tree Farm, notableEventGenre, blues music]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableEventGenre Context triple: [Tyagarah Tea Tree Farm, notableEventGenre, blues music]
-
A.
notableEventMentionedIn
Indicates that a particular notable event is referenced or discussed within a specified source or document.
-
B.
genreOfDescribedEvents
chosen
Indicates that one entity specifies the genre or type category of the events described by another entity.
-
C.
notableEventIncluded
Indicates that a particular notable event is contained within, or forms part of, a larger collection, record, or context.
-
D.
notableEventResponse
Indicates a response, reaction, or consequence that occurs as a result of a notable event.
-
E.
notableAIEvent
Indicates that an event is recognized as significant or influential within the field of artificial intelligence.
- 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_69f76e7cbbf48190891227b14d041139 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0e039481908a4a2666f76c5363 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:13 p.m.