Triple
T803383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BET Award |
E17176
|
entity |
| Predicate | ceremonyIncludes |
P21211
|
FINISHED |
| Object | live performances |
—
|
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: live performances | Statement: [BET Award, ceremonyIncludes, live performances]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ceremonyIncludes Context triple: [BET Award, ceremonyIncludes, live performances]
-
A.
ceremonyType
Indicates the specific kind or category of ceremony associated with an event or relationship.
-
B.
ceremonyNumber
Indicates the specific ordinal or identifying number assigned to a particular ceremony within a set or sequence of ceremonies.
-
C.
ceremonyTiming
Indicates the temporal relationship specifying when a ceremony occurs or is scheduled to occur.
-
D.
ceremonyOrganizedBy
Indicates that a particular ceremony is arranged, planned, or coordinated by a specified organizing entity.
-
E.
ceremonialAssociation
Indicates a relationship where entities are linked through participation in, role within, or connection to a formal ceremony or ritual event.
- F. None of above. chosen
Provenance (4 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_69a49378b9c48190adbf5f62e5b7aca1 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4ace495348190aec66f35ea90bc89 |
completed | March 1, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69a4aa70973c8190adbf08302d1103a9 |
completed | March 1, 2026, 9:06 p.m. |
| PDg | Predicate description generation | batch_69a4ace369b481908ad69de6de99f5e6 |
completed | March 1, 2026, 9:17 p.m. |
Created at: March 1, 2026, 7:38 p.m.