Triple
T32350154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maestro |
E826572
|
entity |
| Predicate | hasReissueProducts |
P203829
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Maestro, hasReissueProducts, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReissueProducts Context triple: [Maestro, hasReissueProducts, true]
-
A.
hasReissueOn
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.
hasReissueModel
Indicates that an entity has a specific model or version that serves as its reissued or updated form.
-
D.
hasReissuePublisher
Indicates that an entity has been republished or reissued by a specified publisher.
-
E.
hasReissueHistory
Indicates that an entity has a record of being reissued or having undergone one or more reissue events in its history.
- F. None of above. chosen
Provenance (4 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_69f34914dfc48190a390cd0720d9e86f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a02145017b08190bd424cc647c08d3b |
completed | May 11, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_6a021338e2b08190980c489ee44c18b3 |
completed | May 11, 2026, 5:34 p.m. |
| PDg | Predicate description generation | batch_6a02144f627c81909ead77e8e6b8f84f |
completed | May 11, 2026, 5:39 p.m. |
Created at: May 1, 2026, 12:49 a.m.