Triple
T11112142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ubhaya Kavichakravarti |
E262782
|
entity |
| Predicate | honorificForSkillIn |
P97325
|
FINISHED |
| Object | poetry |
—
|
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: poetry | Statement: [Ubhaya Kavichakravarti, honorificForSkillIn, poetry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honorificForSkillIn Context triple: [Ubhaya Kavichakravarti, honorificForSkillIn, poetry]
-
A.
honorificForAchievementIn
Indicates that an honorific title or designation is conferred in recognition of an achievement within a particular field, domain, or activity.
-
B.
honorificFunction
Indicates that one entity serves as an honorific title, role, or form of address used in reference to another entity.
-
C.
honorificSense
Indicates that one entity refers to another using an honorific or respectful linguistic form.
-
D.
honorificForAction
Indicates that a particular honorific or respectful form of address is used specifically in connection with performing a given action.
-
E.
honorificType
Indicates the type or category of honorific or formal title associated with an entity in a given context.
- 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_69d6aa9b46cc8190b19f9f0cc45bf322 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79aa42ec4819085a2e802e00d9f02 |
completed | April 9, 2026, 12:25 p.m. |
| PD | Predicate disambiguation | batch_69d7441cf8188190b8095f622c923156 |
completed | April 9, 2026, 6:15 a.m. |
| PDg | Predicate description generation | batch_69d750ca52ec8190a559432a5de106fd |
completed | April 9, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:27 p.m.