Triple
T3024570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1987 Constitution of the Philippines |
E82544
|
entity |
| Predicate | ratifiedByPlebiscite |
P32657
|
FINISHED |
| Object | 1987 |
—
|
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: 1987 | Statement: [1987 Constitution of the Philippines, ratifiedByPlebiscite, 1987]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ratifiedByPlebiscite Context triple: [1987 Constitution of the Philippines, ratifiedByPlebiscite, 1987]
-
A.
ratifiedBy
Indicates that an agreement, treaty, or decision has been formally approved and made officially valid by a specified authority or body.
-
B.
ratificationVote
Indicates a formal vote taken to approve, confirm, or give official sanction to a decision, agreement, or action.
-
C.
ratifiedWith
Indicates that an agreement, treaty, or decision has been formally approved or confirmed through a specified instrument, process, or accompanying document.
-
D.
plebisciteHeldInYear
chosen
Indicates that a plebiscite (a direct vote by the electorate on a specific issue) was held in the specified year.
-
E.
ratifiedOn
Indicates the date or point in time at which an agreement, treaty, or formal decision was officially approved and made valid.
- 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_69ad8b1fb34081908c1b873e2b7273e1 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9abac0288190a30b42674eea501f |
completed | March 8, 2026, 3:50 p.m. |
| PD | Predicate disambiguation | batch_69ad961c430c8190ac48f2e3c7e7c649 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3 p.m.