Triple
T16673867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Shoop Shoop Song (It’s in His Kiss) |
E405168
|
entity |
| Predicate | madeWidelyKnownBy |
P52554
|
FINISHED |
| Object | Cher’s 1990s cover |
—
|
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: Cher’s 1990s cover | Statement: [The Shoop Shoop Song (It’s in His Kiss), madeWidelyKnownBy, Cher’s 1990s cover]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: madeWidelyKnownBy Context triple: [The Shoop Shoop Song (It’s in His Kiss), madeWidelyKnownBy, Cher’s 1990s cover]
-
A.
fameFor
chosen
Indicates that one entity is widely known or recognized specifically because of, or in connection with, another entity.
-
B.
starMadeFamous
Indicates that one entity (such as a work, event, or role) is what caused another entity (typically a person) to become widely known or famous.
-
C.
reconocidaPor
Indicates that an entity is recognized, acknowledged, or honored by another entity.
-
D.
organFamousFor
Indicates that an organ is widely recognized or notable for a particular characteristic, function, or association.
-
E.
celebratedAs
Indicates that one entity is regarded, honored, or widely recognized as having a particular role, status, or distinction.
- 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_69d8838c28748190b3f5967c743940ab |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37d6904008190a79ab30b6d9ccae9 |
completed | April 18, 2026, 12:47 p.m. |
| PD | Predicate disambiguation | batch_69e319bc73908190a0e38bc926b31f10 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:19 a.m.