Triple
T28886899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Golden Peacock Award |
E732589
|
entity |
| Predicate | festivalFoundedBy |
P11844
|
FINISHED |
| Object | Government of India |
—
|
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: Government of India | Statement: [Golden Peacock Award, festivalFoundedBy, Government of India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: festivalFoundedBy Context triple: [Golden Peacock Award, festivalFoundedBy, Government of India]
-
A.
festivalFounded
Indicates that a particular festival was established or created by a specific person, group, or organization.
-
B.
festivalFoundedIn
Indicates that a festival was established or created in a specific year or time period.
-
C.
festivalOrganiser
Indicates that one entity is responsible for planning, coordinating, or managing a festival for another entity or context.
-
D.
wasFoundedBy
chosen
Indicates that an organization, institution, or entity came into existence through the initiating action or establishment by a specific founder or founding group.
-
E.
festivalAlsoKnownAs
Indicates that a festival is referred to by an alternative name or alias.
- 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_69f05b07bdec819080cadfe147aa1f25 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f6617ba4a88190bfc5c305acb4f93f |
completed | May 2, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 7:51 a.m.