Triple
T7298225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tears in Heaven |
E167776
|
entity |
| Predicate | hasAcousticVersion |
P48651
|
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: [Tears in Heaven, hasAcousticVersion, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAcousticVersion Context triple: [Tears in Heaven, hasAcousticVersion, yes]
-
A.
hasKaraokeVersion
Indicates that an entity has a corresponding karaoke (instrumental or sing-along) version of itself.
-
B.
hasAudioFeature
chosen
Indicates that one entity possesses or is associated with a specific audio-related characteristic or property.
-
C.
hasVocals
Indicates that the subject includes or features vocal elements, such as singing or spoken voice, rather than being purely instrumental or non-vocal.
-
D.
hasMusical
Indicates that one entity features, includes, or is associated with a musical work, performance, or musical component.
-
E.
hasLyricalVariant
Indicates that one item has an alternative version that differs in its lyrics while remaining related to the original.
- 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_69c6888c820881909fc68f689fe1c251 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6eb8f83c881909e8eae85410f9659 |
completed | March 27, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69c6e76e67d88190bd3ca6864f45845a |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 3 p.m.