Triple
T28131317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Simon Says |
E711071
|
entity |
| Predicate | isBestKnownSongOf |
P46713
|
FINISHED |
| Object | Ohio Express |
—
|
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: Ohio Express | Statement: [Simon Says, isBestKnownSongOf, Ohio Express]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBestKnownSongOf Context triple: [Simon Says, isBestKnownSongOf, Ohio Express]
-
A.
isOneOfBestKnownSongsBy
chosen
Indicates that the subject song is among the most widely recognized or celebrated songs created by the specified artist or group.
-
B.
isPopularSongOf
Indicates that a song is widely liked, well-known, or frequently enjoyed in relation to a particular entity (such as an artist, album, or context).
-
C.
isPopularSongFrom
Indicates that a song is widely liked, well-known, or frequently played and originates from a particular source, such as an artist, album, or media work.
-
D.
isPopularSongFor
Indicates that a song is widely liked, well-known, or frequently chosen by a particular audience, group, or context.
-
E.
isPopularSong
Indicates that a song is widely liked, well-known, or frequently listened to by many people.
- 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_69ef9b73bd288190a21ae3d6aa14f386 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f6412b8ddc8190bc95eb63bd865ef7 |
completed | May 2, 2026, 6:23 p.m. |
| PD | Predicate disambiguation | batch_69f63c6a8474819091b8c6fe98e3862d |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 9:23 p.m.