Triple
T11428628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | "I'll Be There" |
E270818
|
entity |
| Predicate | isMotownClassic |
P17136
|
FINISHED |
| Object | true |
—
|
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: true | Statement: ["I'll Be There", isMotownClassic, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMotownClassic Context triple: ["I'll Be There", isMotownClassic, true]
-
A.
isPivotalSongIn
Indicates that a song plays a crucial or defining role within a particular work, context, or collection.
-
B.
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.
-
C.
isOneOfBestKnownSongsBy
Indicates that the subject song is among the most widely recognized or celebrated songs created by the specified artist or group.
-
D.
consideredClassic
chosen
Indicates that something is widely regarded or recognized as a classic within a particular field, genre, or context.
-
E.
isClassicEraSongOf
Indicates that a song belongs to the classic era repertoire associated with a particular artist, group, or period.
- 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_69d6aadeef688190874bcecd88b3dd9b |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d806c1bfb881909720c74fe0fa837f |
completed | April 9, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69d7e71436f88190ac7e45a04ea5c987 |
completed | April 9, 2026, 5:51 p.m. |
Created at: April 8, 2026, 9:35 p.m.