Triple
T18212595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Restoration Day (Dominican Republic) |
E436068
|
entity |
| Predicate | restorationWarEndYear |
P16681
|
FINISHED |
| Object | 1865 |
—
|
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: 1865 | Statement: [Restoration Day (Dominican Republic), restorationWarEndYear, 1865]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: restorationWarEndYear Context triple: [Restoration Day (Dominican Republic), restorationWarEndYear, 1865]
-
A.
battleEndYear
Indicates the calendar year in which a particular battle or military engagement concluded.
-
B.
lastWarEnd
Indicates that a specified war or conflict has reached its conclusion at a particular time or event.
-
C.
warEndDate
chosen
Indicates the date on which a particular war or armed conflict officially ended.
-
D.
yearOfSurrender
Indicates the specific calendar year in which an entity formally surrendered or yielded, typically ending its resistance or control.
-
E.
constitutionalRestorationYear
Indicates the year in which a constitution was restored or reinstated after being suspended, replaced, or otherwise not in effect.
- 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_69d8b90dba6481908e119eb9aa4ca0cb |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4e22a26308190a6720b41a9bbfc2d |
completed | April 19, 2026, 2:09 p.m. |
| PD | Predicate disambiguation | batch_69e4332155d88190b106d0dceb4554af |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:32 a.m.