Triple
T29024220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hardwell |
E737541
|
entity |
| Predicate | returnShow |
P176730
|
FINISHED |
| Object | Ultra Music Festival Miami 2022 |
—
|
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: Ultra Music Festival Miami 2022 | Statement: [Hardwell, returnShow, Ultra Music Festival Miami 2022]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: returnShow Context triple: [Hardwell, returnShow, Ultra Music Festival Miami 2022]
-
A.
returnAppearance
Indicates that one entity resumes or restores a previous visual form, style, or outward appearance of another entity or of itself.
-
B.
returns
Indicates that one entity gives or sends something back to another entity, often as a result or outcome of a process or action.
-
C.
returnedFor
Indicates that an entity has been sent, given, or brought back in response to, or on behalf of, another entity or prior action.
-
D.
returnsAs
Indicates that one entity goes back to or resumes a previous state, location, role, or condition associated with another entity.
-
E.
returnsTo
Indicates that an entity goes back to a previous location, state, or entity it was associated with before.
- F. None of above. chosen
Provenance (4 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_69f077ef00fc81909325f084ad37c035 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6e6029a10819098ff21f58079e70e |
completed | May 3, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d5e8188190b1e1c2e5d1b77031 |
completed | May 3, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69f6e60109648190947a64ca4ce81a3a |
completed | May 3, 2026, 6:06 a.m. |
Created at: April 28, 2026, 9:51 a.m.