Triple
T32283188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Breakthrough Prize |
E824754
|
entity |
| Predicate | ceremonyStyle |
P157272
|
FINISHED |
| Object | celebrity-filled ceremony |
—
|
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: celebrity-filled ceremony | Statement: [Breakthrough Prize, ceremonyStyle, celebrity-filled ceremony]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ceremonyStyle Context triple: [Breakthrough Prize, ceremonyStyle, celebrity-filled ceremony]
-
A.
ceremonyType
Indicates the specific kind or category of ceremony associated with an event or relationship.
-
B.
ceremonialDressFeature
Indicates that one entity is a characteristic, component, or distinguishing element of another entity’s ceremonial dress or attire.
-
C.
ceremonyKnownAs
Indicates that a particular ceremony is referred to or recognized by a specific name or title.
-
D.
ceremonialFeatures
chosen
Indicates that something possesses attributes, elements, or characteristics specifically associated with ceremonies or ritual practices.
-
E.
ceremonyIncludes
Indicates that a particular ceremony contains, involves, or encompasses a specified component, activity, or element as part of its structure or proceedings.
- 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_69f3490f404081908450db66884f4334 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bccd1aa88190882a5dbb8100ca1e |
completed | May 3, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69f6b632cf788190a3d0c08cd026b84b |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:43 a.m.