Triple
T18109216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ellipse |
E433427
|
entity |
| Predicate | includesBonusDisc |
P69779
|
FINISHED |
| Object | Ellipse instrumental versions |
—
|
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: Ellipse instrumental versions | Statement: [Ellipse, includesBonusDisc, Ellipse instrumental versions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesBonusDisc Context triple: [Ellipse, includesBonusDisc, Ellipse instrumental versions]
-
A.
hasBonusTrackStatus
Indicates whether an item (such as a track or release) is designated as a bonus track in relation to a primary work or edition.
-
B.
expandedEditionIncludes
Indicates that an expanded edition of a work contains, as part of its content, the material from another specified edition or version.
-
C.
containsAdditionalTracksBeyond
chosen
Indicates that one entity includes more tracks or items than are present in another referenced set or version.
-
D.
seriesIncludes
Indicates that a particular series contains or encompasses the referenced item as one of its constituent parts.
-
E.
supportsBonus
Indicates that one entity provides or enables an additional benefit, reward, or bonus for 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_69d8b90916008190a1f110bd7ced5473 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ddbbfae88190aa77f498dbb9edcb |
completed | April 19, 2026, 1:50 p.m. |
| PD | Predicate disambiguation | batch_69e43313ca788190baa224269e71de49 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:28 a.m.