Triple
T18645373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Live at the Fillmore East (Ten Years After album) |
E455790
|
entity |
| Predicate | hasLiveSound |
P22084
|
FINISHED |
| Object | raw concert atmosphere |
—
|
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: raw concert atmosphere | Statement: [Live at the Fillmore East (Ten Years After album), hasLiveSound, raw concert atmosphere]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLiveSound Context triple: [Live at the Fillmore East (Ten Years After album), hasLiveSound, raw concert atmosphere]
-
A.
hasSound
chosen
Indicates that an entity produces, emits, or is associated with a particular sound.
-
B.
hasSoundSystem
Indicates that an entity is equipped with or includes a sound system as one of its features.
-
C.
hasLiveMusic
Indicates that a place or event features live musical performances as part of its offerings.
-
D.
hasLivePerformanceStyle
Indicates that an entity is associated with a particular style or manner of live performance.
-
E.
containsSound
Indicates that one entity includes, embodies, or produces the sound associated with 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_69d8d38ea1e88190997e9b231190ba6f |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5500d69648190800da65de0c191b8 |
completed | April 19, 2026, 9:58 p.m. |
| PD | Predicate disambiguation | batch_69e478d85864819093cbad5ed9b54878 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:47 a.m.