Triple
T36360148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Black Lion Records |
E895465
|
entity |
| Predicate | hasReissued |
P202654
|
FINISHED |
| Object | Dexter Gordon recordings |
—
|
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: Dexter Gordon recordings | Statement: [Black Lion Records, hasReissued, Dexter Gordon recordings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReissued Context triple: [Black Lion Records, hasReissued, Dexter Gordon recordings]
-
A.
hasReissueOn
chosen
Indicates that an item has been reissued or released again on a specified medium, format, or platform.
-
B.
hasReissueProgram
Indicates that an entity offers a program or process for issuing replacements or updated versions of something previously provided.
-
C.
hasReissueHistory
Indicates that an entity has a record of being reissued or having undergone one or more reissue events in its history.
-
D.
wasReissued
Indicates that an item, such as a document or edition, has been issued again after its original release.
-
E.
hasSubsequentReissue
Indicates that one entity is a later reissued version that follows another entity in sequence.
- 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_69f76e5044248190b390d8887dc03254 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0a54cc8190868c1bfa1590d1a6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:09 p.m.