Triple
T32025669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Engineers Day in India |
E817809
|
entity |
| Predicate | primaryHonoureeTitle |
P43861
|
FINISHED |
| Object | Bharat Ratna 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: Bharat Ratna awardee | Statement: [Engineers Day in India, primaryHonoureeTitle, Bharat Ratna awardee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryHonoureeTitle Context triple: [Engineers Day in India, primaryHonoureeTitle, Bharat Ratna awardee]
-
A.
honoraryTitleGrantedTo
Indicates that an honorary title has been formally conferred upon a particular entity.
-
B.
honoursTitle
Indicates that an entity holds or is designated by a formal honorific or honorary title.
-
C.
honorificTitle
Indicates that one entity serves as a formal honorific or respectful title used to address or refer to another entity.
-
D.
hasHonoraryTitle
Indicates that an entity has been granted a formal honorary title or distinction, typically in recognition of merit or achievement.
-
E.
honoreeRole
chosen
Indicates the specific role, title, or capacity in which an individual is being honored in relation to an award, event, or recognition.
- 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_69f348fb04e4819081f4eab040ed7959 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:17 a.m.