Triple
T18212572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Restoration Day (Dominican Republic) |
E436068
|
entity |
| Predicate | relatedConflictStart |
P104851
|
FINISHED |
| Object | 1863 |
—
|
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: 1863 | Statement: [Restoration Day (Dominican Republic), relatedConflictStart, 1863]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedConflictStart Context triple: [Restoration Day (Dominican Republic), relatedConflictStart, 1863]
-
A.
endedConflict
Indicates that a previously ongoing conflict between entities has been brought to an end.
-
B.
reportedConflict
Indicates that one party has formally reported the existence of a conflict involving another party or situation.
-
C.
conflictBeginsFor
chosen
Indicates the point in time or event at which a conflict starts for a particular party or set of parties.
-
D.
subsequentConflict
Indicates that one conflict occurs after and is temporally subsequent to another conflict.
-
E.
raisedForConflict
Indicates that an issue, concern, or case has been formally brought up due to a conflict between parties or conditions.
- 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.