Triple
T34660508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Good Ol' Boys |
E890092
|
entity |
| Predicate | hasLyricReferenceTo |
P114550
|
FINISHED |
| Object | The Dukes of Hazzard characters |
—
|
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: The Dukes of Hazzard characters | Statement: [Good Ol' Boys, hasLyricReferenceTo, The Dukes of Hazzard characters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLyricReferenceTo Context triple: [Good Ol' Boys, hasLyricReferenceTo, The Dukes of Hazzard characters]
-
A.
hasLyricsIn
Indicates that the lyrics of a work are written or available in a specified language.
-
B.
hasLyricsMentioning
chosen
Indicates that the referenced lyrics explicitly mention or refer to the specified entity.
-
C.
lyricReference
Indicates that one entity (typically a work or text) contains or makes a reference to the lyrics of another entity.
-
D.
containsSongReferencing
Indicates that one entity (such as a work, collection, or playlist) includes at least one song that makes an explicit reference to another specified entity.
-
E.
hasLyric
Indicates that one entity (typically a musical work or track) contains or is associated with the lyrics provided by another entity.
- 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_69f349d906bc8190b2efd9eff237d94b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f727bde8f88190ad746ca515134ca1 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72739c30c81908642eef3feb3afcf |
completed | May 3, 2026, 10:45 a.m. |
Created at: May 1, 2026, 2:04 a.m.