Triple
T8485519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Love for Sale |
E200822
|
entity |
| Predicate | featuresBigBandArrangements |
P21952
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Love for Sale, featuresBigBandArrangements, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresBigBandArrangements Context triple: [Love for Sale, featuresBigBandArrangements, true]
-
A.
hasPianoArrangement
Indicates that one entity has a version or adaptation of it arranged specifically for piano.
-
B.
notableArrangementType
chosen
Indicates that one entity is characterized by or associated with a particular notable type of arrangement or configuration of another entity.
-
C.
hasChoralArrangement
Indicates that one entity is a choral arrangement version or setting of another entity (typically an original musical work).
-
D.
hasSheetMusicAvailability
Indicates that there exists accessible sheet music associated with the referenced musical work or performance.
-
E.
featuresMarchingBands
Indicates that something includes or presents marching bands as part of its content or composition.
- 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_69ca831d7b148190a6e32c1de43ab13b |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe53b359c81908174addcd6e12785 |
completed | March 31, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69cbd107633c8190a36ba50e07876918 |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:12 p.m.