Triple
T23979859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Big Bad Bill (Is Sweet William Now) |
E604476
|
entity |
| Predicate | hasNotableLyricElement |
P104602
|
FINISHED |
| Object | comic narrative |
—
|
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: comic narrative | Statement: [Big Bad Bill (Is Sweet William Now), hasNotableLyricElement, comic narrative]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableLyricElement Context triple: [Big Bad Bill (Is Sweet William Now), hasNotableLyricElement, comic narrative]
-
A.
hasLyric
Indicates that one entity (typically a musical work or track) contains or is associated with the lyrics provided by another entity.
-
B.
hasLyricsIn
Indicates that the lyrics of a work are written or available in a specified language.
-
C.
hasLyricCharacter
Indicates that a musical work or song includes a specific character or persona within its lyrics.
-
D.
hasLyricPhrase
Indicates that one entity (typically a song or musical work) contains or is associated with a specific lyric phrase as part of its textual content.
-
E.
hasLyricsFeature
chosen
Indicates that something possesses a particular characteristic or attribute related to its lyrics.
- 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_69e29543f40c819087700b7a272afb60 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d2bc79688190bc98a2d57b91f5a3 |
completed | April 29, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_69f161578d54819084a8b35496299993 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:27 p.m.