Triple
T31244661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rockestra Theme |
E796656
|
entity |
| Predicate | recordedUnderCollectiveName |
P102130
|
FINISHED |
| Object | Rockestra |
—
|
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: Rockestra | Statement: [Rockestra Theme, recordedUnderCollectiveName, Rockestra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordedUnderCollectiveName Context triple: [Rockestra Theme, recordedUnderCollectiveName, Rockestra]
-
A.
recordedByCollective
chosen
Indicates that an event, action, or piece of data was recorded by a group or collective entity rather than by an individual.
-
B.
hasCollectiveCharacter
Indicates that a group or set of entities is treated as a unified whole, sharing a collective nature or identity rather than being considered solely as separate individuals.
-
C.
usedCollectiveName
Indicates that a group of entities is referred to by a shared collective name.
-
D.
collectivelyKnownAs
Indicates that multiple entities are referred to together under a single shared name or designation.
-
E.
recordedWithArtist
Indicates that one artist participated in a recording together with another artist.
- 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_69f224dc84d0819081f1cb6f9127e6b1 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fcef654d588190b29ecc76678d1aa0 |
completed | May 7, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69fcecdb97f48190b382b7d13be92dc0 |
completed | May 7, 2026, 7:49 p.m. |
Created at: April 29, 2026, 9:11 p.m.