Triple
T22963085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pieces of a Dream |
E570959
|
entity |
| Predicate | hasTrackSelectionCriterion |
P86752
|
FINISHED |
| Object | commercial success |
—
|
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: commercial success | Statement: [Pieces of a Dream, hasTrackSelectionCriterion, commercial success]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTrackSelectionCriterion Context triple: [Pieces of a Dream, hasTrackSelectionCriterion, commercial success]
-
A.
hasComparisonCriterion
Indicates that one entity is used as the basis or standard by which another entity is compared or evaluated.
-
B.
hasTrack
Indicates that one entity possesses, includes, or is associated with a specific track (such as a path, course, or recorded item).
-
C.
hasSelectionFor
Indicates that one entity holds or specifies a chosen option, subset, or configuration on behalf of another entity.
-
D.
containsTrackType
Indicates that one entity includes or is associated with a specific type or category of track.
-
E.
hasSelectionStandard
chosen
Indicates that there is a defined criterion or set of rules used to choose or filter items, options, or entities.
- 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_69e245b212a88190b5259caf51606084 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f181f66fbc8190a4a7b73d17537132 |
completed | April 29, 2026, 3:58 a.m. |
| PD | Predicate disambiguation | batch_69ef3b9101f48190a06c69dff26c6441 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:47 p.m.