Triple
T17399728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blossom |
E423053
|
entity |
| Predicate | hasLiveStudioAudience |
P27043
|
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: [Blossom, hasLiveStudioAudience, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLiveStudioAudience Context triple: [Blossom, hasLiveStudioAudience, true]
-
A.
hasLiveAudienceCapability
Indicates that an entity is capable of supporting or engaging with a live, in-person audience.
-
B.
hasLiveBroadcast
Indicates that a live broadcast is currently being transmitted or available for the referenced entity.
-
C.
hasSpectators
chosen
Indicates that an event, activity, or occurrence is being watched or attended by one or more spectators.
-
D.
offersLiveStreaming
Indicates that one entity provides the capability for real-time (live) streaming of content to another entity or audience.
-
E.
isLiveRecording
Indicates that the recording was captured during a live performance or event rather than produced in a studio or through post-production.
- 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_69d889d710288190bf0f4762801fefae |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43ac0596481908c400916d5c1b971 |
completed | April 19, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69e3b02e6cc88190986e85e64ce9383e |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:45 a.m.