Triple
T6279725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bombshell |
E140749
|
entity |
| Predicate | performedInConcert |
P55120
|
FINISHED |
| Object | 2015 one-night-only Broadway concert |
—
|
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: 2015 one-night-only Broadway concert | Statement: [Bombshell, performedInConcert, 2015 one-night-only Broadway concert]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performedInConcert Context triple: [Bombshell, performedInConcert, 2015 one-night-only Broadway concert]
-
A.
performsMusicIn
Indicates that an entity presents or plays music within a particular venue, event, or context.
-
B.
performedSongFor
Indicates that one entity performed a song specifically for another entity as the intended audience or recipient.
-
C.
hasPerformedLiveIn
chosen
Indicates that an entity has given a live performance in a specified location or venue.
-
D.
performedSong
Indicates that an entity (such as an artist or performer) has given a performance of a particular song.
-
E.
notableLivePerformanceEvent
Indicates that an entity is a significant or widely recognized live performance event associated with another entity (such as an artist, work, or venue).
- 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_69c008cc158881908df6ec94a911c736 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c063dc55d48190b5ed48a50f3a742e |
completed | March 22, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69c05608a5608190b22a1fdc4060470d |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:26 p.m.