Triple
T25041067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ARIA Hall of Fame induction |
E627108
|
entity |
| Predicate | typicalHonourees |
P58949
|
FINISHED |
| Object | Australian recording artists |
—
|
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: Australian recording artists | Statement: [ARIA Hall of Fame induction, typicalHonourees, Australian recording artists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalHonourees Context triple: [ARIA Hall of Fame induction, typicalHonourees, Australian recording artists]
-
A.
typicalHonoree
chosen
Indicates that an entity is the usual or characteristic recipient of an honor, award, or recognition associated with another entity.
-
B.
hasHonorees
Indicates that one entity is recognized or celebrated by listing another entity or entities as its honorees.
-
C.
typicalAwardedBy
Indicates the usual or standard agent (such as a person or organization) that confers or grants a particular award.
-
D.
typicalNominees
Indicates that the specified entities are the usual or commonly selected candidates or recipients associated with something.
-
E.
yearHonored
Indicates the specific year in which an entity received an honor, award, or formal recognition.
- 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_69e2ff2a2c088190be513727ee8bfe78 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f7764ab1fc81909f9348db87bd7692 |
completed | May 3, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f76905d9c88190b1ee810bc9ab644f |
completed | May 3, 2026, 3:25 p.m. |
Created at: April 18, 2026, 6:08 a.m.