Triple
T120338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Academy of Motion Picture Arts and Sciences |
E2430
|
entity |
| Predicate | eventOrganized |
P123
|
FINISHED |
| Object | Academy Awards 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: Academy Awards ceremony | Statement: [Academy of Motion Picture Arts and Sciences, eventOrganized, Academy Awards ceremony]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventOrganized Context triple: [Academy of Motion Picture Arts and Sciences, eventOrganized, Academy Awards ceremony]
-
A.
event
Indicates that there exists an occurrence or happening involving one or more entities, typically situated in time and possibly space.
-
B.
eventRole
Indicates the specific function, capacity, or part an entity plays within an event or occurrence.
-
C.
organizes
chosen
Indicates that one entity arranges, coordinates, or structures activities, items, or people into an ordered or planned form for a particular purpose.
-
D.
announcementOccasion
Indicates the specific event, context, or circumstance on the basis of which an announcement is made.
-
E.
participatedInEvent
Indicates that an entity took part in or was actively involved in a specific event.
- 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_69a2506c5428819085c28a8884790e29 |
completed | Feb. 28, 2026, 2:18 a.m. |
| NER | Named-entity recognition | batch_69a258fd278481908ad4498e03f38e2f |
completed | Feb. 28, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69a25647fe6081908cb0405266d35ff5 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:24 a.m.