Triple
T18232689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | What Da Hook Gon Be |
E436582
|
entity |
| Predicate | hasChorusTheme |
P129123
|
FINISHED |
| Object | crafting a song hook |
—
|
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: crafting a song hook | Statement: [What Da Hook Gon Be, hasChorusTheme, crafting a song hook]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChorusTheme Context triple: [What Da Hook Gon Be, hasChorusTheme, crafting a song hook]
-
A.
hasChorusLyricTheme
chosen
Indicates that the chorus lyrics of a musical work center around or express a particular theme or subject.
-
B.
hasChorus
Indicates that something (typically a song or musical piece) includes a chorus section as part of its structure.
-
C.
hasChorusBy
Indicates that something (typically a musical work or song) includes a chorus section that is performed, written, or provided by a specified entity.
-
D.
hasChorusIn
Indicates that a musical work includes a chorus section within the specified part or segment.
-
E.
hasChorusStyle
Indicates that an entity is associated with a particular style or manner in which a chorus is performed or structured.
- 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_69d8b9103a8081908bbb0836fef10efd |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4f4b414308190bc7dd8e73c0a362c |
completed | April 19, 2026, 3:28 p.m. |
| PD | Predicate disambiguation | batch_69e4332336cc8190808b9c70c888ba65 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:33 a.m.