Triple
T29329376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flash |
E743734
|
entity |
| Predicate | smallBeginningsChartPerformance |
P60345
|
FINISHED |
| Object | Billboard Hot 100 (United States) |
—
|
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: Billboard Hot 100 (United States) | Statement: [Flash, smallBeginningsChartPerformance, Billboard Hot 100 (United States)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: smallBeginningsChartPerformance Context triple: [Flash, smallBeginningsChartPerformance, Billboard Hot 100 (United States)]
-
A.
chartPerformance
Indicates how well something ranks or behaves on a chart or leaderboard over a given period.
-
B.
totalStarts
Indicates the total number of times an entity has been started or initiated across all relevant instances or periods.
-
C.
firstPerformanceStatus
Indicates the status or outcome of an entity’s initial or debut performance.
-
D.
chartingSingle
chosen
Indicates that an entity appears on a music chart as a single track release.
-
E.
notableChartSuccessIn
Indicates that an entity has achieved significant or noteworthy success on music or performance charts within a specified region, market, or chart system.
- 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_69f09125f784819080f4e9fce9fe624f |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f6689891608190a721be24599c4edd |
completed | May 2, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_69f660f2e3708190ab658652bcfc04d0 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 1:28 p.m.