Triple
T28914404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bold and Reckless |
E733315
|
entity |
| Predicate | hasReleaseVariations |
P113983
|
FINISHED |
| Object | different versions on different single releases |
—
|
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: different versions on different single releases | Statement: [Bold and Reckless, hasReleaseVariations, different versions on different single releases]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReleaseVariations Context triple: [Bold and Reckless, hasReleaseVariations, different versions on different single releases]
-
A.
hasVariantsIn
chosen
Indicates that an entity exists in multiple alternative forms or versions within a specified context or set.
-
B.
hasDistributionVariant
Indicates that one entity is a variant or alternative form of another entity specifically in terms of its distribution characteristics or pattern.
-
C.
hasRelease
Indicates that an entity (such as a product, work, or version) has a specific release instance or event associated with it.
-
D.
hasVariantSeries
Indicates a relationship where one entity is a variant or alternative series derived from or associated with another series.
-
E.
hasVariant
Indicates that one entity exists as an alternative form, version, or variation of another entity.
- 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_69f05b0a5cc0819094828367ae204b70 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69ff9a25407c81909faa86e72a7a9d17 |
completed | May 9, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69ff99c613688190a03b2f93d5ccad2b |
completed | May 9, 2026, 8:32 p.m. |
Created at: April 28, 2026, 8:13 a.m.