Triple
T23578103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Freek'n You |
E582118
|
entity |
| Predicate | subsequentReleaseType |
P50239
|
FINISHED |
| Object | commercial single |
—
|
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: commercial single | Statement: [Freek'n You, subsequentReleaseType, commercial single]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subsequentReleaseType Context triple: [Freek'n You, subsequentReleaseType, commercial single]
-
A.
subsequentReleaseFormat
chosen
Indicates that one media release is issued in a different format that chronologically follows an earlier release of the same content.
-
B.
followUpRelease
Indicates that one release occurs subsequently as a continuation or update to a previous release.
-
C.
subsequentPublication
Indicates that one publication was released after another in time, making it a later or follow-up work relative to the first.
-
D.
laterReReleasedBy
Indicates that an entity was re-released at a later time by a specified agent or organization.
-
E.
releaseOf
Indicates the act or event of something being set free, made available, or discharged from a prior state of containment, control, or restriction.
- 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_69e248f8d8248190acd5aee77f0d1709 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1afd7dbe88190b05ff03f952bf7c3 |
completed | April 29, 2026, 7:14 a.m. |
| PD | Predicate disambiguation | batch_69f118bcc0b08190b25a8dddfd461a0e |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:39 p.m.