Triple
T12224562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Live from Soho (EP) |
E291314
|
entity |
| Predicate | hasAudienceSetting |
P56401
|
FINISHED |
| Object | intimate live performance |
—
|
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: intimate live performance | Statement: [Live from Soho (EP), hasAudienceSetting, intimate live performance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAudienceSetting Context triple: [Live from Soho (EP), hasAudienceSetting, intimate live performance]
-
A.
hasAudience
Indicates that an entity is intended to be received, viewed, or engaged with by a particular group of people.
-
B.
hasAudiencePolicy
Indicates that there is a specified rule or policy governing which audience or group is allowed to access, view, or receive something.
-
C.
hasAudienceSize
Indicates the relationship between an entity and the number of people or size of group that receives, views, or engages with it.
-
D.
audienceSetting
chosen
Indicates the context or environment in which an audience is situated or addressed.
-
E.
hasAudienceReach
Indicates the extent or scope of people or groups that are exposed to, can access, or are targeted by a particular entity, message, or activity.
- 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.