Triple
T32738216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | On the Track |
E837148
|
entity |
| Predicate | includesCoverVersionsOf |
P159864
|
FINISHED |
| Object | early jazz standards |
—
|
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: early jazz standards | Statement: [On the Track, includesCoverVersionsOf, early jazz standards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesCoverVersionsOf Context triple: [On the Track, includesCoverVersionsOf, early jazz standards]
-
A.
isCoveredBy
Indicates that one entity is physically or conceptually overlaid, protected, or enclosed by another entity.
-
B.
isCoverFor
Indicates that one entity serves as a protective or concealing layer, substitute, or front for another entity or activity.
-
C.
hasVariantCovers
chosen
Indicates that one entity has alternative or different versions of its covers associated with it.
-
D.
isCoveredIn
Indicates that one entity has its surface or area overlaid, coated, or blanketed by another substance or material.
-
E.
containsCoverOf
Indicates that one entity includes within it a cover or covering representation of 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_69f34936e1748190b797e406e4e9293a |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a0204dafcc08190868a6f3eab162505 |
completed | May 11, 2026, 4:33 p.m. |
| PD | Predicate disambiguation | batch_6a0202dc60348190a140bb9da906f5b6 |
completed | May 11, 2026, 4:25 p.m. |
Created at: May 1, 2026, 1:12 a.m.