Triple
T32557715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 94th Academy Awards |
E832135
|
entity |
| Predicate | incidentInvolvedPerson |
P113889
|
FINISHED |
| Object | Will Smith |
—
|
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: Will Smith | Statement: [94th Academy Awards, incidentInvolvedPerson, Will Smith]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: incidentInvolvedPerson Context triple: [94th Academy Awards, incidentInvolvedPerson, Will Smith]
-
A.
incidentWith
chosen
Indicates that one entity is involved in, affected by, or associated with a particular incident or event together with another entity.
-
B.
constantInvolved
Indicates that a constant participates in or is directly involved in the specified relation, operation, or context.
-
C.
incidentName
Indicates the specific name or label assigned to an incident within a system or context.
-
D.
rightInvolved
Indicates that an entity is involved in or associated with a legal or formal right held, exercised, or affected in a given context.
-
E.
relativeInvolvedInEvent
Indicates that a person’s relative participates in, is affected by, or is otherwise involved in a particular 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_69f34926b9848190ace47d2dd0a0de7c |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c60206e48190b5139a3ad31330bc |
completed | May 3, 2026, 3:50 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2a14b081908162923dfbf0a6f4 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 1:03 a.m.