Triple
T33637166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Academy Award for Best Foreign Language Film (India's official entry) |
E861728
|
entity |
| Predicate | renamingEffectiveFromYear |
P1742
|
FINISHED |
| Object | 2020 |
—
|
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: 2020 | Statement: [Academy Award for Best Foreign Language Film (India's official entry), renamingEffectiveFromYear, 2020]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: renamingEffectiveFromYear Context triple: [Academy Award for Best Foreign Language Film (India's official entry), renamingEffectiveFromYear, 2020]
-
A.
renamingEffectiveFromCeremony
Indicates the point in time, defined by a specific ceremony, from which a renaming action becomes valid and officially takes effect.
-
B.
renamedYear
chosen
Indicates the year in which an entity underwent a renaming or change of name.
-
C.
redesignationYear
Indicates the year in which something was officially redesignated, renamed, or assigned a new status or classification.
-
D.
renamedInPeriod
Indicates that an entity underwent a renaming during a specified time period.
-
E.
wasRenamedIn
Indicates that an entity changed its name to a different one at or during a specific time or 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_69f3498280c48190bcc3494017d14234 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5740fc81909774a4f65201a3ff |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:42 a.m.