Triple
T23489616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maha Vir Chakra |
E570632
|
entity |
| Predicate | confersHonorific |
P141044
|
FINISHED |
| Object | use of post-nominal letters MVC |
—
|
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: use of post-nominal letters MVC | Statement: [Maha Vir Chakra, confersHonorific, use of post-nominal letters MVC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: confersHonorific Context triple: [Maha Vir Chakra, confersHonorific, use of post-nominal letters MVC]
-
A.
confersHonorificStatus
chosen
Indicates that one entity formally grants an honorific title, rank, or status to another entity.
-
B.
hasHonorificStatus
Indicates that an entity holds or is assigned a particular honorific title, rank, or status in relation to another entity.
-
C.
isHonorific
Indicates that one entity functions as an honorific title or respectful form of address applied to another entity.
-
D.
honorificIndicates
Indicates that one entity uses an honorific title or respectful form of address to refer to or address another entity.
-
E.
honorificType
Indicates the type or category of honorific or formal title associated with an entity in a given context.
- 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_69e245b0b01481908f636939bedd804c |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a7dae8cc8190bf74d1bdb0fc6c60 |
completed | April 29, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69f0620ac3608190b36916261ea50f54 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 6:04 p.m.