Triple
T29208409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 36th Annual Grammy Awards |
E740479
|
entity |
| Predicate | liveEvent |
P1664
|
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: [36th Annual Grammy Awards, liveEvent, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liveEvent Context triple: [36th Annual Grammy Awards, liveEvent, true]
-
A.
originallyBroadcastLive
Indicates that the content was transmitted to audiences in real time at the time of its first broadcast, rather than being pre-recorded.
-
B.
notableLiveFeature
Indicates that an entity is distinguished or recognized for a particular live performance, broadcast, or real-time feature.
-
C.
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.
-
D.
livePerformanceFeature
Indicates that one entity is included or highlighted as a component of another entity’s live performance.
-
E.
event
chosen
Indicates that there exists an occurrence or happening involving one or more entities, typically situated in time and possibly space.
- 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_69f07cb974108190b7e86ca489a6ebb6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f66402f5348190be752c897f8e5e2d |
completed | May 2, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f65c24f8b48190af81b575f3c15be5 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 12:10 p.m.