Triple
T27776639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beautiful World Tour |
E699206
|
entity |
| Predicate | tourForComeback |
P72456
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Beautiful World Tour, tourForComeback, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tourForComeback Context triple: [Beautiful World Tour, tourForComeback, true]
-
A.
madeComeback
Indicates that an entity returned to a previous level of success, performance, or prominence after a period of decline, absence, or setback.
-
B.
returnedToTour
chosen
Indicates that an entity resumed or went back to participating in a tour after having left or paused it.
-
C.
comebackContext
Indicates the situational background, circumstances, or prior events that frame or motivate a comeback or return.
-
D.
comebackWin
Indicates a victory achieved by overcoming a prior deficit or losing position during the contest or event.
-
E.
isOnComebackAlbum
Indicates that an entity (such as a song or track) appears on an album that marks a return or resurgence for the artist after a period of reduced activity or absence.
- 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_69f6379ab2248190ac5eadadb9bd5e3b |
completed | May 2, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69f6318ae6f08190b3f85f9201046a15 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 5:06 p.m.