Triple
T37086756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen of Malwa |
E918308
|
entity |
| Predicate | honorificForActivity |
P65546
|
FINISHED |
| Object | just governance |
—
|
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: just governance | Statement: [Queen of Malwa, honorificForActivity, just governance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honorificForActivity Context triple: [Queen of Malwa, honorificForActivity, just governance]
-
A.
honorificForAction
Indicates that a particular honorific or respectful form of address is used specifically in connection with performing a given action.
-
B.
honorificFunction
Indicates that one entity serves as an honorific title, role, or form of address used in reference to another entity.
-
C.
honorificType
Indicates the type or category of honorific or formal title associated with an entity in a given context.
-
D.
honorificSense
Indicates that one entity refers to another using an honorific or respectful linguistic form.
-
E.
honorificForAchievementIn
chosen
Indicates that an honorific title or designation is conferred in recognition of an achievement within a particular field, domain, or activity.
- 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_69f76e9952b88190a6fe01ba01476520 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:14 p.m.