Triple
T395630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Academy Award for Best Original Song |
E8976
|
entity |
| Predicate | ceremonyFrequency |
P2205
|
FINISHED |
| Object | annual |
—
|
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: annual | Statement: [Academy Award for Best Original Song, ceremonyFrequency, annual]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ceremonyFrequency Context triple: [Academy Award for Best Original Song, ceremonyFrequency, annual]
-
A.
ceremonyNumber
Indicates the specific ordinal or identifying number assigned to a particular ceremony within a set or sequence of ceremonies.
-
B.
ceremonyType
Indicates the specific kind or category of ceremony associated with an event or relationship.
-
C.
awardedFrequency
chosen
Indicates how often an award or recognition is given within a specified time period.
-
D.
ceremonialAssociation
Indicates a relationship where entities are linked through participation in, role within, or connection to a formal ceremony or ritual event.
-
E.
ceremonialUse
Indicates that something is used in a ritual, religious, or formal ceremony rather than for ordinary or practical purposes.
- 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_69a2e7f55c60819097aff65ea2ca2832 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec792dd081909b6b18a854139f8c |
completed | Feb. 28, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69a2e96bd3848190a66ca14dfbd26da5 |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.