Triple
T3125754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | All Falls Down |
E65291
|
entity |
| Predicate | chartingStatus |
P4919
|
FINISHED |
| Object | commercially successful single |
—
|
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: commercially successful single | Statement: [All Falls Down, chartingStatus, commercially successful single]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chartingStatus Context triple: [All Falls Down, chartingStatus, commercially successful single]
-
A.
hasCharting
Indicates that one entity provides or supports charting or graphical data visualization capabilities for another entity.
-
B.
chartingVersionBy
Indicates that one entity serves as the versioning or revision source by which another entity’s chart or graphical representation is defined or organized.
-
C.
chartPerformance
chosen
Indicates how well something ranks or behaves on a chart or leaderboard over a given period.
-
D.
chartType
Indicates the specific kind or category of chart used to visually represent data in a given context.
-
E.
chartName
Indicates the specific title or label assigned to a chart that identifies or describes it.
- 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_69ad8580c72481909672d37acf647893 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada52e9f348190aa15b2c0d252719f |
completed | March 8, 2026, 4:34 p.m. |
| PD | Predicate disambiguation | batch_69ad9df62e548190b053e1478deed467 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:04 p.m.