Triple
T21612942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Park MGM |
E533355
|
entity |
| Predicate | hasResidentShow |
P24949
|
FINISHED |
| Object | various concert residencies |
—
|
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: various concert residencies | Statement: [Park MGM, hasResidentShow, various concert residencies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasResidentShow Context triple: [Park MGM, hasResidentShow, various concert residencies]
-
A.
hasResidentShowLocation
Indicates that a location is the regular or primary venue where a resident show is held.
-
B.
hasResidentArtist
Indicates that one entity serves as the resident artist associated with or based at another entity.
-
C.
residencyShow
chosen
Indicates a performance arrangement where an artist or group repeatedly presents a show at the same venue over an extended period.
-
D.
hasOwnShow
Indicates that an entity is the primary host or central figure of a dedicated show or program associated with them.
-
E.
hasNotableResident
Indicates that an entity is or has been a well-known or distinguished resident of a particular place or location.
- 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_69e0c46411108190bba0d4176dffc9f3 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef3ba8d7cc8190a59706896a4c073a |
completed | April 27, 2026, 10:34 a.m. |
| PD | Predicate disambiguation | batch_69e69665fe8c8190af7e38785db188b2 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:33 p.m.