Triple
T33764733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Wicked Trilogy |
E865196
|
entity |
| Predicate | featuresGuestMusicians |
P154364
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [The Wicked Trilogy, featuresGuestMusicians, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresGuestMusicians Context triple: [The Wicked Trilogy, featuresGuestMusicians, yes]
-
A.
featuresMusician
Indicates that something (such as a work, event, or recording) prominently includes or showcases a particular musician.
-
B.
hasGuestMusicians
chosen
Indicates that an event, performance, or recording includes musicians who participate as guests rather than as regular or primary members.
-
C.
featuresVariousArtists
Indicates that something (typically a creative work) includes contributions from multiple distinct artists rather than a single primary artist.
-
D.
featuresDJ
Indicates that an entity includes or presents a DJ as part of its offering or composition.
-
E.
featuresArtistAs
Indicates that one entity includes or presents another entity in the role of an artist (e.g., a work, event, or product featuring a specific 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_69f3498d3b748190aa3c4006c1f32f38 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a021706e21c81909b83e2b4d9c4130c |
completed | May 11, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_6a0216861214819097d2177755bc19d7 |
completed | May 11, 2026, 5:48 p.m. |
Created at: May 1, 2026, 1:45 a.m.