Triple
T22293091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vishnudas Bhave Natya Samaroh |
E551046
|
entity |
| Predicate | honoursRoleOf |
P51002
|
FINISHED |
| Object | pioneer dramatist |
—
|
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: pioneer dramatist | Statement: [Vishnudas Bhave Natya Samaroh, honoursRoleOf, pioneer dramatist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honoursRoleOf Context triple: [Vishnudas Bhave Natya Samaroh, honoursRoleOf, pioneer dramatist]
-
A.
honourOf
Indicates that one entity is the source, bearer, or cause of another entity’s honor, prestige, or distinguished recognition.
-
B.
honoursSystemRole
Indicates that one entity respects, preserves, or correctly applies the designated system-level role of another entity or process.
-
C.
honorsRoleAs
Indicates that one entity shows respect, recognition, or deference to another entity specifically in their official position or function.
-
D.
honorsRole
chosen
Indicates that one entity formally recognizes and respects the position, title, or role held by another entity.
-
E.
honoursPosition
Indicates that one entity holds or is recognized with an honorary or distinguished position in relation to another entity.
- 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_69e11e45fb848190a1b2ae21296e3a5f |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1560de3508190951ad0806ae3cc0d |
completed | April 29, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69e72ffa438481908f80879aef2a589b |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:41 p.m.