Triple
T11649589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Helios Records |
E276865
|
entity |
| Predicate | catalogueRelationship |
P19933
|
FINISHED |
| Object | uses previously issued Hyperion masters |
—
|
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: uses previously issued Hyperion masters | Statement: [Helios Records, catalogueRelationship, uses previously issued Hyperion masters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: catalogueRelationship Context triple: [Helios Records, catalogueRelationship, uses previously issued Hyperion masters]
-
A.
subjectRelation
Indicates that one entity stands in a specified relational role or connection to another entity.
-
B.
titleRelation
Indicates a relationship where one entity serves as the title, designation, or formal name associated with another entity.
-
C.
belongsToCatalogOf
chosen
Indicates that one item is included within, or is a member of, a particular catalog or collection.
-
D.
valueRelation
Indicates a comparative or associative relationship between the values or magnitudes of two or more entities.
-
E.
catalogueType
Indicates the classification or category assigned to an item within a catalogue or cataloging system.
- 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_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a2cea9308190a13f7dd995ea07a4 |
completed | April 10, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69d85ddc780481909a3bc63832fe2bd2 |
completed | April 10, 2026, 2:18 a.m. |
Created at: April 8, 2026, 9:39 p.m.