Triple
T1410910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PB |
E31800
|
entity |
| Predicate | usedAfterNameOf |
P26625
|
FINISHED |
| Object | Padma Bhushan awardee |
—
|
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: Padma Bhushan awardee | Statement: [PB, usedAfterNameOf, Padma Bhushan awardee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAfterNameOf Context triple: [PB, usedAfterNameOf, Padma Bhushan awardee]
-
A.
namedAfter
Indicates that one entity has been given its name in honor of, or derived from, another entity.
-
B.
namedAfterSince
Indicates that one entity has borne the name of another entity starting from a specific point in time.
-
C.
laterNamed
Indicates that an entity was given a new name at a later time, linking its original identity to its subsequent name.
-
D.
usedWithSurname
Indicates that something (typically a given name or title) is used together with a particular surname in naming or reference.
-
E.
usedBefore
Indicates that one entity was utilized or applied prior to the use or occurrence of another entity.
- F. None of above. chosen
Provenance (4 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_69a49919a994819086528951bc224775 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c3e1da988190bc7c187e193539b6 |
completed | March 1, 2026, 10:55 p.m. |
| PD | Predicate disambiguation | batch_69a4bf048b648190ab77d9b45cb4855f |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4bf8158ac8190b8360ecccc2980bc |
completed | March 1, 2026, 10:36 p.m. |
Created at: March 1, 2026, 7:59 p.m.