Triple
T1405744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King of Thailand |
E31686
|
entity |
| Predicate | legalPowers |
P21124
|
FINISHED |
| Object | power to sign legislation |
—
|
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: power to sign legislation | Statement: [King of Thailand, legalPowers, power to sign legislation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalPowers Context triple: [King of Thailand, legalPowers, power to sign legislation]
-
A.
legalAuthorityOver
Indicates that one entity has the recognized power or right to make, enforce, or adjudicate rules or decisions concerning another entity.
-
B.
typeOfPowerGranted
chosen
Indicates the specific kind or category of power or authority that is conferred from one entity to another.
-
C.
legalAuthorityType
Indicates the specific kind or category of legal authority that governs, authorizes, or regulates an entity or action.
-
D.
legalAct
Indicates that an entity performs, enacts, or is involved in a formal legal action, measure, or proceeding under a legal framework.
-
E.
legalAuthorityLevel
Indicates the degree or rank of formal legal power or jurisdiction an entity holds in relation to another or within 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_69a49918e1f88190ba610f9dc8114578 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c3bc55a08190a4dfe13a5378aff3 |
completed | March 1, 2026, 10:54 p.m. |
| PD | Predicate disambiguation | batch_69a4bf030a388190bc82d30b9233e873 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.