Triple
T27775934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Honeymoon Tour |
E699184
|
entity |
| Predicate | hasSetlistLengthRange |
P152768
|
FINISHED |
| Object | 18–21 songs |
—
|
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: 18–21 songs | Statement: [The Honeymoon Tour, hasSetlistLengthRange, 18–21 songs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSetlistLengthRange Context triple: [The Honeymoon Tour, hasSetlistLengthRange, 18–21 songs]
-
A.
hasSetlistScope
Indicates that a setlist is associated with, or limited to, a particular scope or context (such as a specific event, tour, or performance).
-
B.
hasSetlistType
Indicates that an event or performance is associated with a particular type or category of setlist.
-
C.
hasSetlistSource
Indicates that a setlist is derived from, documented by, or associated with a particular source or reference.
-
D.
setlistCharacteristic
chosen
Indicates that a particular property or feature characterizes or describes a musical setlist.
-
E.
hasApproximateNumberOfMusicians
Indicates that an entity is associated with an estimated or approximate count of musicians involved 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_69ef6a4b5a9081909c9111396c2be3d2 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69fd0b92f42881908cd77e3f058adcc2 |
completed | May 7, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fd0a3d68d4819094d92040f7c48d7c |
completed | May 7, 2026, 9:55 p.m. |
Created at: April 27, 2026, 5:06 p.m.