Triple
T25041876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ARIA Award for Best Urban Album (as part of A.B. Original) |
E627134
|
entity |
| Predicate | recognizedArtist |
P601
|
FINISHED |
| Object | A.B. Original |
—
|
NE NERFINISHED |
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: A.B. Original | Statement: [ARIA Award for Best Urban Album (as part of A.B. Original), recognizedArtist, A.B. Original]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recognizedArtist Context triple: [ARIA Award for Best Urban Album (as part of A.B. Original), recognizedArtist, A.B. Original]
-
A.
coveredArtist
Indicates that one artist has performed or recorded a cover version of another artist’s original work.
-
B.
mentionsArtist
Indicates that one entity explicitly refers to or cites an artist in its content or context.
-
C.
selectedArtist
Indicates that a particular artist has been chosen or designated from a set of possible artists.
-
D.
notableArtist
chosen
Indicates that the subject is an artist who is widely recognized or distinguished for their work.
-
E.
primaryArtist
Indicates that an entity is the main or lead artist responsible for a creative work, as opposed to supporting or contributing artists.
- 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_69e2ff2b4c80819087c916b2b16241b9 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f48b9b687881908fd87a2f5fa0b1e7 |
completed | May 1, 2026, 11:16 a.m. |
| PD | Predicate disambiguation | batch_69f48060597c8190a4414e4e4fcb1fec |
completed | May 1, 2026, 10:28 a.m. |
Created at: April 18, 2026, 6:08 a.m.