Triple
T19645940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Woodstock: Music from the Original Soundtrack and More |
E471670
|
entity |
| Predicate | includesCrowdSounds |
P124232
|
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: [Woodstock: Music from the Original Soundtrack and More, includesCrowdSounds, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesCrowdSounds Context triple: [Woodstock: Music from the Original Soundtrack and More, includesCrowdSounds, true]
-
A.
includesAddedSound
Indicates that one entity contains or incorporates an additional sound element beyond the original or primary audio content.
-
B.
containsSound
chosen
Indicates that one entity includes, embodies, or produces the sound associated with another entity.
-
C.
soundCategory
Indicates the classification relationship where a sound is assigned to a particular category or type of sound.
-
D.
followsSoundOf
Indicates that one entity moves or directs its attention by tracking the source or direction of a sound produced by another entity.
-
E.
soundEffects
Indicates that one entity produces, contains, or is associated with sound effects used to accompany or enhance another entity.
- 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_69d8e51395348190ac1416d46dfc6db0 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e641250e108190a707452fefc87041 |
completed | April 20, 2026, 3:07 p.m. |
| PD | Predicate disambiguation | batch_69e514e941008190898d978d7bde91e4 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:44 p.m.