Triple
T18818909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parade |
E460208
|
entity |
| Predicate | hasChartingSingles |
P111778
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Parade, hasChartingSingles, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChartingSingles Context triple: [Parade, hasChartingSingles, yes]
-
A.
hasHitSingleOnChart
chosen
Indicates that an entity (such as an artist or song) has achieved at least one single that appeared on a specified music chart.
-
B.
hasChart
Indicates that one entity is associated with, represented by, or documented through a chart belonging to or describing it.
-
C.
hasChartedIn
Indicates that something (such as a song, album, or work) has appeared on an official ranking or popularity chart within a specified context (such as a country, chart type, or time period).
-
D.
hasNotableChartingStatus
Indicates that an entity has achieved a specific, noteworthy position or performance on an official chart or ranking.
-
E.
hasCharting
Indicates that one entity provides or supports charting or graphical data visualization capabilities for another entity.
- 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_69d8dcf94c288190a06dea029ae4b223 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5a6b8b7d88190a8828746176776ea |
completed | April 20, 2026, 4:08 a.m. |
| PD | Predicate disambiguation | batch_69e48d1b10ec8190985c6fb5766ff981 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:55 a.m.