Triple
T28914342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bastille |
E733313
|
entity |
| Predicate | hasGlobalHitSong |
P64808
|
FINISHED |
| Object | Pompeii |
—
|
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: Pompeii | Statement: [Bastille, hasGlobalHitSong, Pompeii]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGlobalHitSong Context triple: [Bastille, hasGlobalHitSong, Pompeii]
-
A.
hasHitSingleOnChart
Indicates that an entity (such as an artist or song) has achieved at least one single that appeared on a specified music chart.
-
B.
hasInternationalHitSingle
chosen
Indicates that an entity (typically a musical artist or group) has released at least one single that achieved notable popularity or chart success in multiple countries.
-
C.
hasSpecialSong
Indicates that one entity possesses or is associated with a particular song that is unique, distinctive, or specially designated for it.
-
D.
hasSong
Indicates that one entity possesses, features, or includes a particular song.
-
E.
hasInstrumentalHit
Indicates that an entity (typically an artist or group) has created or released a successful or notable instrumental piece of music.
- 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_69f05b0a5cc0819094828367ae204b70 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c2198208190a3954086c22cfcbf |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 8:13 a.m.