Triple
T26487830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rao Bahadur |
E664871
|
entity |
| Predicate | typicallyBestowedUpon |
P136988
|
FINISHED |
| Object | Indian officials |
—
|
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: Indian officials | Statement: [Rao Bahadur, typicallyBestowedUpon, Indian officials]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicallyBestowedUpon Context triple: [Rao Bahadur, typicallyBestowedUpon, Indian officials]
-
A.
traditionallyBestowedOn
chosen
Indicates that something is customarily or historically given, granted, or conferred upon a particular recipient according to tradition.
-
B.
selfBestowedTitle
Indicates that an entity has given a title or designation to itself, rather than receiving it from others.
-
C.
blessedWith
Indicates that one entity has received a positive gift, talent, quality, or advantage attributed to another source.
-
D.
grantedHonor
Indicates that one entity has formally bestowed an honor, award, or distinction upon another entity.
-
E.
grantedOnOccasionOf
Indicates that something (such as a right, benefit, or status) is conferred specifically in connection with, or as a result of, a particular occasion 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_69ee883bc85481909885f92415cbce33 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69feba0f09508190b3e871c62b19ec7f |
completed | May 9, 2026, 4:37 a.m. |
| PD | Predicate disambiguation | batch_69feb957fe7c8190969fb31a6d1a59c8 |
completed | May 9, 2026, 4:34 a.m. |
Created at: April 27, 2026, 12:31 a.m.