Triple
T26843699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stink |
E675852
|
entity |
| Predicate | hasLinerNote |
P178769
|
FINISHED |
| Object | “Kids Don’t Follow” intro police bust recording |
—
|
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: “Kids Don’t Follow” intro police bust recording | Statement: [Stink, hasLinerNote, “Kids Don’t Follow” intro police bust recording]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLinerNote Context triple: [Stink, hasLinerNote, “Kids Don’t Follow” intro police bust recording]
-
A.
hasLinerNotesWrittenBy
Indicates that the liner notes of an item (such as an album or release) are authored by a specified agent.
-
B.
hasAuthorNote
Indicates that an entity includes or is associated with a specific author-provided note or commentary.
-
C.
hasLyric
Indicates that one entity (typically a musical work or track) contains or is associated with the lyrics provided by another entity.
-
D.
hasLyricNarrator
Indicates that a musical or lyrical work is associated with a specific narrator who voices or presents its lyrics.
-
E.
hasAdditionalLyrics
Indicates that an entity (such as a song or track) includes extra or supplementary lyrics beyond a primary or original set.
- F. None of above. chosen
Provenance (4 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_69eee9b8d5e88190a07d3455c0fbb21f |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f71422adac8190a5ceb32dcf820833 |
completed | May 3, 2026, 9:23 a.m. |
| PD | Predicate disambiguation | batch_69f712764d2c819081b64b27e5de4a13 |
completed | May 3, 2026, 9:16 a.m. |
| PDg | Predicate description generation | batch_69f71421e8d08190807ccfb15d0f0ddb |
completed | May 3, 2026, 9:23 a.m. |
Created at: April 27, 2026, 5:09 a.m.