Triple
T11308090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boomiverse |
E267765
|
entity |
| Predicate | hasPart |
P35
|
FINISHED |
| Object | Shine On |
E434387
|
NE 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: Shine On | Statement: [Boomiverse, hasPart, Shine On]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Shine On Context triple: [Boomiverse, hasPart, Shine On]
-
A.
Shine On
chosen
"Shine On" is a song featured on James Blunt's 2007 studio album "All the Lost Souls."
-
B.
Shine On
"Shine On" is a studio album by Canadian singer-songwriter Sarah McLachlan, known for its introspective lyrics and lush, melodic pop sound.
-
C.
Shine It On
"Shine It On" is a song by the Allman Brothers Band featured on their 1990 album "Seven Turns."
-
D.
Shine On Brightly
Shine On Brightly is Procol Harum’s 1968 progressive rock album best known for its ambitious, suite-like compositions and early fusion of rock with classical influences.
-
E.
Shine
"Shine" is a breakthrough 1993 rock single by Collective Soul that became their signature hit and a defining song of 1990s post-grunge.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d6aaca5c24819083db46a30d86cb34 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9bf87d88190904c2d174578ebbf |
completed | April 9, 2026, 6:02 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e50a70022081908bc74185003a3503 |
completed | April 19, 2026, 5:01 p.m. |
Created at: April 8, 2026, 9:32 p.m.