Triple
T38463052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BlizzCon 2013 |
E912497
|
entity |
| Predicate | hasConcertPerformer |
P17435
|
FINISHED |
| Object | Blink-182 |
E93369
|
NE 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: Blink-182 | Statement: [BlizzCon 2013, hasConcertPerformer, Blink-182]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConcertPerformer Context triple: [BlizzCon 2013, hasConcertPerformer, Blink-182]
-
A.
performedInConcertBy
Indicates that an action, piece, or performance was carried out jointly by multiple participants as part of the same concert event.
-
B.
hasLivePerformanceWith
Indicates that two or more entities participate together in the same live performance event.
-
C.
hasNotablePerformer
chosen
Indicates that an entity features or is associated with a performer who is particularly prominent, famous, or otherwise noteworthy.
-
D.
hasLivePerformanceRole
Indicates that an entity holds or fulfills a specific role in a live performance.
-
E.
hasFanPerformances
Indicates that an entity has associated performances created or carried out by fans.
- F. None of above.
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_69f76e861d8c81908559031dc66e3c15 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41ccb4d9b08190b7896dda59475a35 |
completed | June 29, 2026, 1:39 a.m. |
| PD | Predicate disambiguation | batch_6a037a1e32108190897356d6a7fed879 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:31 p.m.