Triple
T27066969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bhranti Bilas |
E685198
|
entity |
| Predicate | isWidelyCelebratedFor |
P52554
|
FINISHED |
| Object | Uttam Kumar’s dual role |
—
|
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: Uttam Kumar’s dual role | Statement: [Bhranti Bilas, isWidelyCelebratedFor, Uttam Kumar’s dual role]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isWidelyCelebratedFor Context triple: [Bhranti Bilas, isWidelyCelebratedFor, Uttam Kumar’s dual role]
-
A.
celebratedAs
Indicates that one entity is regarded, honored, or widely recognized as having a particular role, status, or distinction.
-
B.
fameFor
chosen
Indicates that one entity is widely known or recognized specifically because of, or in connection with, another entity.
-
C.
celebratedThrough
Indicates that something is honored, recognized, or observed by means of a particular activity, medium, or practice.
-
D.
isCelebratedAs
Indicates that an entity is recognized, honored, or regarded in a particular role, status, or capacity.
-
E.
organFamousFor
Indicates that an organ is widely recognized or notable for a particular characteristic, function, or association.
- 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_69ef14835fcc81908bd737b4267ae528 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f622ea4d9081909696af9f5078f2e9 |
completed | May 2, 2026, 4:14 p.m. |
| PD | Predicate disambiguation | batch_69f620e0b37481909a280574decbd443 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 8:25 a.m.