Triple
T28959754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ultra Music Festival |
E731863
|
entity |
| Predicate | alsoHeldInPast |
P126989
|
FINISHED |
| Object | Virginia Key, Miami |
—
|
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: Virginia Key, Miami | Statement: [Ultra Music Festival, alsoHeldInPast, Virginia Key, Miami]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alsoHeldInPast Context triple: [Ultra Music Festival, alsoHeldInPast, Virginia Key, Miami]
-
A.
alsoHeld
Indicates that the same event, position, or role was held or occupied by another entity in addition to the primary one.
-
B.
hasPreviouslyBeenHeldIn
Indicates that an entity was located, confined, or kept in a particular place or container at some time in the past.
-
C.
hasPreviouslyBeenHeldAt
chosen
Indicates that an event or activity has taken place at a particular location at some time in the past.
-
D.
previouslyIn
Indicates that an entity was located in, part of, or associated with another entity at some earlier time, but is not necessarily so now.
-
E.
usedInPastBy
Indicates that an entity was previously utilized or employed by another entity at some time in the past.
- 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_69f043ee242c8190b063248b417c5a69 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f65bc00e148190b2dc4ce5d4245f1b |
completed | May 2, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69f659d02f1c8190831758ac52bb54e4 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 8:49 a.m.