Triple
T18000699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shape of My Heart |
E430617
|
entity |
| Predicate | isClosingTrackOnSomeEditions |
P130083
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Shape of My Heart, isClosingTrackOnSomeEditions, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isClosingTrackOnSomeEditions Context triple: [Shape of My Heart, isClosingTrackOnSomeEditions, yes]
-
A.
isClosingTrackVariationOf
Indicates that one track is a variant or alternate version specifically used as the closing track of another track or release.
-
B.
isClosingTrackOf
Indicates that a track serves as the final or last track on a specified release, album, or recording.
-
C.
isClosingTrackOn
Indicates that a track serves as the final (closing) track on a specified release or collection.
-
D.
hasDifferentEditions
Indicates that an entity exists in multiple distinct versions or editions that differ in some characteristics.
-
E.
hasEditionIn
Indicates that one entity has a specific edition or version that exists or is available in another entity (such as a particular format, language, or location).
- 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_69d8b90364248190a37381adea932f42 |
completed | April 10, 2026, 8:46 a.m. |
| NER | Named-entity recognition | batch_69e4b3e82ca48190aeb53e03c95ef223 |
completed | April 19, 2026, 10:52 a.m. |
| PD | Predicate disambiguation | batch_69e3f90039e4819080527f860dca042e |
completed | April 18, 2026, 9:34 p.m. |
| PDg | Predicate description generation | batch_69e42d8d68288190a05dc5d7803cf823 |
completed | April 19, 2026, 1:19 a.m. |
Created at: April 10, 2026, 10:23 a.m.