Triple
T38503326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Juan MacLean |
E919897
|
entity |
| Predicate | performsLiveAs |
P49471
|
FINISHED |
| Object | DJ set |
—
|
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: DJ set | Statement: [The Juan MacLean, performsLiveAs, DJ set]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performsLiveAs Context triple: [The Juan MacLean, performsLiveAs, DJ set]
-
A.
isPerformedLiveBy
Indicates that an action, event, or performance occurs in real time in front of an audience and is carried out by the specified entity.
-
B.
performsAs
chosen
Indicates that one entity takes on, enacts, or fulfills the role, function, or character of another entity.
-
C.
hasLiveActionPerformer
Indicates that a character, role, or entity is portrayed or performed by a specific live-action (real-life) performer.
-
D.
livePerformer
Indicates that an entity performs an artistic or entertainment act live, typically in front of an audience.
-
E.
hasLivePerformanceStatus
Indicates whether an entity’s live performance is occurring, scheduled, completed, or otherwise characterized by a specific performance status.
- 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_69f76e9ddd4481908f8c04439d848f9d |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff76ac40988190a34d858b5472ee2b |
completed | May 9, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69ff760a90948190a12fcb80e6e3e14b |
completed | May 9, 2026, 5:59 p.m. |
Created at: May 3, 2026, 4:31 p.m.