Triple
T10515067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 81st Academy Awards |
E248009
|
entity |
| Predicate | liveBroadcast |
P34446
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [81st Academy Awards, liveBroadcast, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liveBroadcast Context triple: [81st Academy Awards, liveBroadcast, yes]
-
A.
broadcastLiveFrom
Indicates that an event or program is being transmitted in real time from a specific location or source.
-
B.
hasLiveBroadcast
chosen
Indicates that a live broadcast is currently being transmitted or available for the referenced entity.
-
C.
originallyBroadcastLive
Indicates that the content was transmitted to audiences in real time at the time of its first broadcast, rather than being pre-recorded.
-
D.
offersLiveStreaming
Indicates that one entity provides the capability for real-time (live) streaming of content to another entity or audience.
-
E.
recordedAsLive
Indicates that an audio or video performance was captured in real time before an audience or in a live setting, rather than produced or edited in a studio environment.
- 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_69d381c4aa948190942e1d803143fb0e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d509cbacb08190a446c864b97823ad |
completed | April 7, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69d4fb919ea08190bcc1193e2014d437 |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:27 p.m.