Triple
T3756585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First Philippine Republic |
E82061
|
entity |
| Predicate | constitutionAdoptedOn |
P2497
|
FINISHED |
| Object | 1899-01-21 |
—
|
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: 1899-01-21 | Statement: [First Philippine Republic, constitutionAdoptedOn, 1899-01-21]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: constitutionAdoptedOn Context triple: [First Philippine Republic, constitutionAdoptedOn, 1899-01-21]
-
A.
constitutionAdoptedIn
Indicates the event or relationship in which a constitution is formally adopted in a specific place or jurisdiction.
-
B.
lastConstitutionAdopted
Indicates that a particular constitution was the most recently adopted constitution of a given political entity or jurisdiction.
-
C.
constitutionAdopted
Indicates that a particular constitution has been formally accepted and put into effect by the relevant authority or polity.
-
D.
charterAdoptedIn
Indicates that a charter was formally adopted or enacted at a specific time or in a specific place.
-
E.
dateOfConstitutionSigning
chosen
Indicates the date on which a constitution was formally signed or adopted.
- 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_69ad8b1db40081908b61ffa6b78afd4d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcbbe7a6081909b0f835a77941300 |
completed | March 8, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69adc04c851c8190ae5eaebf36df539b |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:35 p.m.