Triple
T28467842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S Club Juniors |
E720343
|
entity |
| Predicate | performedAsSupportActFor |
P88834
|
FINISHED |
| Object | S Club 7 |
—
|
NE NERFINISHED |
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: S Club 7 | Statement: [S Club Juniors, performedAsSupportActFor, S Club 7]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performedAsSupportActFor Context triple: [S Club Juniors, performedAsSupportActFor, S Club 7]
-
A.
wasOpeningActFor
chosen
Indicates that one performer or group served as the preliminary act appearing before another, main performer or group in a live event or show.
-
B.
performedOnStageWith
Indicates that two or more entities appeared and performed together in the same stage event or production.
-
C.
performedInConcertBy
Indicates that an action, piece, or performance was carried out jointly by multiple participants as part of the same concert event.
-
D.
performedSongFor
Indicates that one entity performed a song specifically for another entity as the intended audience or recipient.
-
E.
performedOnTourWith
Indicates that one entity carried out a tour in conjunction with, or as part of, another entity’s tour.
- 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_69f01a58a67c819097936d9e8da8d6e6 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f7bbf906d8819099020e548dd56bc9 |
completed | May 3, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a2dcf88190a7c9e109e41267be |
completed | May 3, 2026, 9:09 p.m. |
Created at: April 28, 2026, 2:46 a.m.