Triple
T36091767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Hell Not Hallelujah Tour |
E1043937
|
entity |
| Predicate | promotionalTourFor |
P96880
|
FINISHED |
| Object | studio album |
—
|
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: studio album | Statement: [The Hell Not Hallelujah Tour, promotionalTourFor, studio album]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: promotionalTourFor Context triple: [The Hell Not Hallelujah Tour, promotionalTourFor, studio album]
-
A.
tourPromotion
chosen
Indicates a promotional relationship where an entity is being advertised, marketed, or highlighted as part of a tour or touring event.
-
B.
promotionalFor
Indicates that one entity serves to advertise, market, or otherwise promote another entity, such as a product, service, event, or brand.
-
C.
tourPromoter
Indicates a relationship where an entity organizes, markets, or manages a tour or series of live events for another entity.
-
D.
performedTour
Indicates that an entity carried out or conducted a tour for another entity or at a particular place and time.
-
E.
notableTour
Indicates that an entity is recognized for having a significant or well-known tour associated with it.
- 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_69f76e32d60c8190ba781ffaaab4aa3d |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7cec454a88190a9f3bbee2b856636 |
completed | May 3, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f7c8977c288190997a892ec5f756ed |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:08 p.m.