Triple
T21361493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tradition Records |
E526790
|
entity |
| Predicate | reissueHistory |
P136885
|
FINISHED |
| Object | catalog later reissued by other labels |
—
|
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: catalog later reissued by other labels | Statement: [Tradition Records, reissueHistory, catalog later reissued by other labels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reissueHistory Context triple: [Tradition Records, reissueHistory, catalog later reissued by other labels]
-
A.
hasReissueHistory
chosen
Indicates that an entity has a record of being reissued or having undergone one or more reissue events in its history.
-
B.
renewalHistory
Indicates the record of past renewal events or actions that have occurred for a given entity over time.
-
C.
wasReissued
Indicates that an item, such as a document or edition, has been issued again after its original release.
-
D.
reissueIncludes
Indicates that a reissued version of something contains or incorporates the referenced item as part of that reissue.
-
E.
reissueFeature
Indicates that an existing item (such as a product, document, or media release) is being issued again, typically with updates, changes, or in a new edition or format.
- 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_69e0b51d8a308190b09113b3b3f9bc15 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e8b06a4e4c8190923741bfae0e4234 |
completed | April 22, 2026, 11:26 a.m. |
| PD | Predicate disambiguation | batch_69e6162bbfc88190a3e75859941b2638 |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 5:08 p.m.