Triple
T34733496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buddhist Dhammaraja |
E1001275
|
entity |
| Predicate | roleOfKing |
P41822
|
FINISHED |
| Object | protector of the Dharma |
—
|
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: protector of the Dharma | Statement: [Buddhist Dhammaraja, roleOfKing, protector of the Dharma]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleOfKing Context triple: [Buddhist Dhammaraja, roleOfKing, protector of the Dharma]
-
A.
roleInKingship
chosen
Indicates that an entity holds or plays a specific role or position within a system of kingship or royal authority.
-
B.
kingOf
Indicates that one entity holds the position or role of king in relation to another entity, typically a territory, people, or domain.
-
C.
monarchicalRole
Indicates that one entity holds or is assigned a specific position, function, or office within a monarchical system of governance.
-
D.
roleInMonarchyPeriod
Indicates that an entity held a specific role or position during a defined period of a monarchy.
-
E.
alsoKingOf
Indicates that an entity who is king of one place is simultaneously king of another place as well.
- 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_69f76daf739881909ed3554f98a2b433 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 3:59 p.m.