Triple
T27952036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FFRR Records |
E703451
|
entity |
| Predicate | releasedWork |
P153729
|
FINISHED |
| Object | dance music compilations |
—
|
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: dance music compilations | Statement: [FFRR Records, releasedWork, dance music compilations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: releasedWork Context triple: [FFRR Records, releasedWork, dance music compilations]
-
A.
releaseOfWork
Indicates that one entity makes a work (such as a product, publication, or creative output) publicly available or officially issued.
-
B.
releaseEventOfWork
Indicates that a particular event involves or marks the release of a specific work (such as a creative, artistic, or intellectual product).
-
C.
workReleased
Indicates that a creative or intellectual work has been made publicly available or officially published.
-
D.
issuedWork
chosen
Indicates that an entity has formally produced, published, or released a particular work.
-
E.
hasWorkReleasedIn
Indicates that a creative work (such as a book, film, or album) was released or made publicly available in a particular time period or location.
- 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_69ef840c8b2c8190946ae9522774ba51 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f6a8df16a88190a23820e64a3b1f92 |
completed | May 3, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 27, 2026, 7:25 p.m.