Triple
T27775941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Honeymoon Tour |
E699184
|
entity |
| Predicate | hasOfficialMerchandiseLine |
P45835
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [The Honeymoon Tour, hasOfficialMerchandiseLine, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOfficialMerchandiseLine Context triple: [The Honeymoon Tour, hasOfficialMerchandiseLine, yes]
-
A.
fanMerchandiseAvailable
Indicates that merchandise related to a fan or fandom is available for purchase or acquisition.
-
B.
hasOfficialLogo
Indicates that one entity is the formally recognized logo or emblem representing another entity.
-
C.
hasOfficialStyle
Indicates that an entity possesses a formally recognized style, manner, or form as defined by an authoritative source or standard.
-
D.
hasMerchandiseTieIn
chosen
Indicates that one entity has a commercial or promotional product or line (merchandise) that is directly tied to, branded with, or derived from another entity.
-
E.
hasOfficialArtwork
Indicates that an entity is associated with an officially sanctioned piece of artwork representing 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_69ef6a4b5a9081909c9111396c2be3d2 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 27, 2026, 5:06 p.m.