Triple
T37154246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Republic Act No. 10360 |
E920449
|
entity |
| Predicate | requiresPlebiscite |
P116987
|
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: [Republic Act No. 10360, requiresPlebiscite, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresPlebiscite Context triple: [Republic Act No. 10360, requiresPlebiscite, yes]
-
A.
plebisciteSupervisedBy
Indicates that a plebiscite is conducted under the oversight, control, or monitoring authority of a specified supervising entity.
-
B.
plebisciteHeld
Indicates that a public vote or referendum has been conducted to decide a specific issue or proposal.
-
C.
requiresPopularApproval
chosen
Indicates that an action, decision, or change can only proceed if it has been approved or supported by a sufficiently large portion of the relevant population.
-
D.
voteRequirement
Indicates the minimum level or type of vote needed for a decision, action, or status to be valid or approved.
-
E.
requiresElectionBy
Indicates that one entity can only assume a role, status, or condition if it is chosen through a formal election process conducted by another entity or group.
- 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_69f76e9f87c08190b4c8f7fafbd8345a |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a002f0839fc8190a874d3b0d0826d7e |
completed | May 10, 2026, 7:08 a.m. |
| PD | Predicate disambiguation | batch_6a002eae7b6481909974b321e2789b7e |
completed | May 10, 2026, 7:07 a.m. |
Created at: May 3, 2026, 4:15 p.m.