Triple
T29957401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Elixir |
E760939
|
entity |
| Predicate | hostsPerformerType |
P153862
|
FINISHED |
| Object | EDM artists |
—
|
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: EDM artists | Statement: [The Elixir, hostsPerformerType, EDM artists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostsPerformerType Context triple: [The Elixir, hostsPerformerType, EDM artists]
-
A.
hostsArtistsType
chosen
Indicates that an entity serves as a host or venue for artists of a specified type or category.
-
B.
performerType
Indicates the role or category of performer responsible for carrying out an action or participating in an event.
-
C.
typicalPerformerCount
Indicates the usual or standard number of performers involved in carrying out the associated activity or event.
-
D.
typicalPerformers
Indicates the entities that most commonly or characteristically perform a given action or role.
-
E.
featuresPerformerType
Indicates that something includes or highlights a performer of a specified type (e.g., musician, actor, or other performance role).
- 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_69f22466327481908ba6db916837bece |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b7b03488190b1db5fde4c7dd6e5 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 6:27 p.m.