Triple
T15929225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parliament of Bhutan |
E386279
|
entity |
| Predicate | monarchParticipatesInLegislation |
P4525
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Parliament of Bhutan, monarchParticipatesInLegislation, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monarchParticipatesInLegislation Context triple: [Parliament of Bhutan, monarchParticipatesInLegislation, yes]
-
A.
monarchInvolved
chosen
Indicates that a monarch participates in, is associated with, or plays a role in a particular event, action, or situation.
-
B.
legislativeActOf
Indicates a relationship where a legislative act is authored, enacted, or formally issued by a specific legislative body or authority.
-
C.
monarchIn
Indicates that a person serves as the ruling monarch of a specified country, state, or territory.
-
D.
canInitiateLegislation
Indicates that the subject has the authority or power to formally propose or introduce new legislation or legal measures.
-
E.
canAdviseMonarchOn
Indicates that one entity has the authority or capacity to provide counsel or guidance to a monarch on matters of decision or policy.
- 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_69d86da750008190987eb26be3f6c118 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e172b48b308190bc430b2308cbc75b |
completed | April 16, 2026, 11:37 p.m. |
| PD | Predicate disambiguation | batch_69e142cf5c548190a931f7b58144cd31 |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:52 a.m.