Triple
T37641836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Executive orders of the President of the Philippines |
E936635
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | executive order series |
C846
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: executive order series Context triple: [Executive orders of the President of the Philippines, instanceOf, executive order series]
-
A.
executive order
chosen
An executive order is a formal directive issued by a head of the executive branch, such as a president or governor, that manages operations of the government and has the force of law within the scope of existing statutory or constitutional authority.
-
B.
federal order
A federal order is a binding directive or mandate issued by a national-level authority or court that governs actions, procedures, or policies within its jurisdiction.
-
C.
executive authority
Executive authority is the power and responsibility to implement, enforce, and administer laws and policies within a governing system or organization.
-
D.
United States presidential reorganization plan
A United States presidential reorganization plan is a formal proposal submitted by the President to Congress to restructure, consolidate, or transfer functions within the executive branch to improve its efficiency and effectiveness.
-
E.
executive branch guidance
Executive branch guidance consists of nonbinding directives, interpretations, or policy statements issued by executive agencies or officials to explain, implement, or clarify laws and regulations without going through formal rulemaking.
- F. None of above.
Provenance (1 batch)
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_69f76ed31d8881908405da6c6d2f0463 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:18 p.m.