Triple
T27215776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meghnad |
E681134
|
entity |
| Predicate | honorificMeaningOfName |
P167770
|
FINISHED |
| Object | conqueror of Indra |
—
|
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: conqueror of Indra | Statement: [Meghnad, honorificMeaningOfName, conqueror of Indra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honorificMeaningOfName Context triple: [Meghnad, honorificMeaningOfName, conqueror of Indra]
-
A.
honorificSuffixMeaning
Indicates that a particular honorific suffix conveys a specific meaning or nuance in how someone is addressed.
-
B.
honorificSense
Indicates that one entity refers to another using an honorific or respectful linguistic form.
-
C.
honorificNameOf
Indicates that one entity is the honorific or respectful name or title used to refer to another entity.
-
D.
honorificOrigin
Indicates that an honorific title or form of address originates from, or is derived from, a particular source, culture, language, or context.
-
E.
honoraryTitleMeaning
Indicates that an honorary title is conferred to recognize or symbolize a particular status, achievement, or role without granting the full formal powers or responsibilities of that title.
- 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_69eefac9f64c8190a07490fe0c8b72a3 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f66cf092c881908d7034c9c2bc61d5 |
completed | May 2, 2026, 9:30 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69f66c59de9881909ebbb7b0ae7ab495 |
completed | May 2, 2026, 9:27 p.m. |
Created at: April 27, 2026, 9:41 a.m.