Triple
T1231214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hero (song) |
E26445
|
entity |
| Predicate | hasChartSuccess |
P4919
|
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: [Hero (song), hasChartSuccess, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChartSuccess Context triple: [Hero (song), hasChartSuccess, yes]
-
A.
hasChartingCover
Indicates that one entity serves as the charting or graphical representation (cover) of another entity’s data or content.
-
B.
reissueChartSuccess
Indicates that the process of reissuing a chart has completed successfully.
-
C.
chartName
Indicates the specific title or label assigned to a chart that identifies or describes it.
-
D.
chartPerformance
chosen
Indicates how well something ranks or behaves on a chart or leaderboard over a given period.
-
E.
hasStatePie
Indicates that an entity possesses or is associated with a specific state-related pie (e.g., a pie representing or originating from a particular state).
- 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_69a4948571c88190a9191e451e6035fd |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4be5a25348190a0665b6324c4d8f5 |
completed | March 1, 2026, 10:31 p.m. |
| PD | Predicate disambiguation | batch_69a4bb65d61c8190bf0424ea0019a98b |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:47 p.m.