Triple
T32025668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Engineers Day in India |
E817809
|
entity |
| Predicate | primaryHonoureeName |
P206153
|
FINISHED |
| Object | Sir Mokshagundam Visvesvaraya |
E236259
|
NE 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: Sir Mokshagundam Visvesvaraya | Statement: [Engineers Day in India, primaryHonoureeName, Sir Mokshagundam Visvesvaraya]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryHonoureeName Context triple: [Engineers Day in India, primaryHonoureeName, Sir Mokshagundam Visvesvaraya]
-
A.
honoreeGivenName
Indicates the given (first) name of a person who is being honored or recognized.
-
B.
honoreeMiddleName
Indicates the middle name held by the person who is being honored.
-
C.
honoreeField
Indicates that one entity is recognized or designated as the honoree associated with another entity, such as an award, event, or dedication.
-
D.
honorsPerson
Indicates that one entity formally recognizes, respects, or pays tribute to a specific person.
-
E.
honoreeKnownFor
Indicates that an honoree is recognized or celebrated specifically for a particular work, achievement, contribution, or notable attribute.
- F. None of above. chosen
Provenance (5 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_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a34665a199481909267f54fa223b3be |
completed | June 18, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7fb9f88190b384b1b68200aef0 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 12:17 a.m.