Triple
T24207947
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alive/Worldwide Tour |
E600450
|
entity |
| Predicate | isReunionOf |
P147224
|
FINISHED |
| Object | original Kiss lineup |
—
|
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: original Kiss lineup | Statement: [Alive/Worldwide Tour, isReunionOf, original Kiss lineup]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isReunionOf Context triple: [Alive/Worldwide Tour, isReunionOf, original Kiss lineup]
-
A.
hasReunion
Indicates that a reunion event or gathering occurs between the related entities.
-
B.
reunionWith
chosen
Indicates that two or more entities come back together after a period of separation or absence.
-
C.
reunionType
Indicates the specific kind or category of reunion event that relates the involved entities.
-
D.
reunionLineupIncluded
Indicates that a specific person or entity was part of the official lineup for a reunion event of a group or organization.
-
E.
reunitedFor
Indicates that entities who were previously separated have come back together or been brought back into association.
- 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_69e2953344c48190875730c7d52112a0 |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f27ca717e8819093fdc82fa063d9a6 |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c43e55688190b55fc20274ed471c |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:50 p.m.