Triple
T28886929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Govinda Govinda |
E732591
|
entity |
| Predicate | isAcclaimedWorkOf |
P17579
|
FINISHED |
| Object | Buddhadeb Dasgupta |
—
|
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: Buddhadeb Dasgupta | Statement: [Govinda Govinda, isAcclaimedWorkOf, Buddhadeb Dasgupta]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAcclaimedWorkOf Context triple: [Govinda Govinda, isAcclaimedWorkOf, Buddhadeb Dasgupta]
-
A.
acclaimedFor
Indicates that an entity receives widespread praise or recognition specifically for another entity, such as a work, achievement, or contribution.
-
B.
notableAwardWork
chosen
Indicates that a work is the specific creation (e.g., book, film, artwork) for which an award or honor was given.
-
C.
namedForNotableWork
Indicates that one entity is named in honor of another entity’s notable work or achievement.
-
D.
recognizesWorkOf
Indicates that one entity acknowledges, identifies, or gives credit to the work or contributions produced by another entity.
-
E.
hasArtistOfNotableWork
Indicates that an entity is associated with the artist who created a notable work related to that entity.
- 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_69f65b14512c8190a40e70319dcc54cd |
completed | May 2, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f659d02f1c8190831758ac52bb54e4 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 7:51 a.m.