Triple
T20196623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1,000 Hours |
E493100
|
entity |
| Predicate | hasReissueContext |
P129495
|
FINISHED |
| Object | later reissued on CD via compilation |
—
|
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: later reissued on CD via compilation | Statement: [1,000 Hours, hasReissueContext, later reissued on CD via compilation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReissueContext Context triple: [1,000 Hours, hasReissueContext, later reissued on CD via compilation]
-
A.
hasReissuePeriod
Indicates the time span during which something (such as a document, license, or product) may be reissued or renewed.
-
B.
hasReissueProgram
Indicates that an entity offers a program or process for issuing replacements or updated versions of something previously provided.
-
C.
hasReissuePublisher
Indicates that an entity has been republished or reissued by a specified publisher.
-
D.
hasReissueHistory
Indicates that an entity has a record of being reissued or having undergone one or more reissue events in its history.
-
E.
hasSubsequentReissue
chosen
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_69da6268a034819081cbd9ea5a1c9475 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66ad99d50819090ddb7b546c65321 |
completed | April 20, 2026, 6:05 p.m. |
| PD | Predicate disambiguation | batch_69e55b14c9d8819095453d0504d9222f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:37 p.m.