Triple
T30858399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Independent Spirit Award for Best Editing |
E785992
|
entity |
| Predicate | ceremonyHeldInAdvanceOf |
P14854
|
FINISHED |
| Object | Academy Awards |
—
|
NE NERFINISHED |
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 | Statement: [Independent Spirit Award for Best Editing, ceremonyHeldInAdvanceOf, Academy Awards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ceremonyHeldInAdvanceOf Context triple: [Independent Spirit Award for Best Editing, ceremonyHeldInAdvanceOf, Academy Awards]
-
A.
ceremonyHeld
Indicates that a formal ceremony or ritual event has taken place at a particular time and/or location.
-
B.
ceremonyKnownAs
Indicates that a particular ceremony is referred to or recognized by a specific name or title.
-
C.
ceremonyTiming
chosen
Indicates the temporal relationship specifying when a ceremony occurs or is scheduled to occur.
-
D.
ceremonyTargeted
Indicates that a ceremony is specifically directed toward, intended for, or focused on a particular entity as its target.
-
E.
ceremonyPresidedBy
Indicates that a ceremony is overseen, led, or officially conducted by a particular person or authority.
- 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_69f224b91c14819084e764832fe67a57 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f691a665c481908e0a9a2aef659563 |
completed | May 3, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69f68b7d2794819092fef8a63f4f3de8 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:46 p.m.