Triple
T12224603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sweeter Live |
E291316
|
entity |
| Predicate | includesLiveVersionsOf |
P45804
|
FINISHED |
| Object | songs from Sweeter |
—
|
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: songs from Sweeter | Statement: [Sweeter Live, includesLiveVersionsOf, songs from Sweeter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesLiveVersionsOf Context triple: [Sweeter Live, includesLiveVersionsOf, songs from Sweeter]
-
A.
hasLiveVersions
chosen
Indicates that an entity has one or more recorded or documented live-performance versions of itself.
-
B.
hasLiveActionVersion
Indicates that an entity has a corresponding adaptation or version produced in live-action (with real actors and physical settings) rather than animation or other non-live formats.
-
C.
hasVersionIn
Indicates that one entity exists as a specific version or variant within the context, format, or system represented by another entity.
-
D.
hasMultipleVersions
Indicates that an entity exists in more than one distinct version or revision.
-
E.
notableLiveVersion
Indicates that one work is a particularly significant or well-known live performance version of another work.
- 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_69d6ab668acc8190963ba424049d6aee |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d920e312708190b4aede2e21f5f697 |
completed | April 10, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69d91c3d669c81908eea7ad61122d275 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:51 p.m.