Triple
T997022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Ryswick |
E21517
|
entity |
| Predicate | signedOnDate |
P439
|
FINISHED |
| Object | 20 September 1697 |
—
|
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: 20 September 1697 | Statement: [Treaty of Ryswick, signedOnDate, 20 September 1697]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signedOnDate Context triple: [Treaty of Ryswick, signedOnDate, 20 September 1697]
-
A.
dateSigned
chosen
Indicates the specific date on which an agreement, document, or contract was formally signed.
-
B.
signedOnAnniversaryOf
Indicates that an agreement or document was signed on the anniversary date of a specific prior event or reference point.
-
C.
signedDuring
Indicates that an agreement, document, or contract was signed within a specified time period or during a particular event.
-
D.
agreementSigned
Indicates that a formal agreement or contract has been officially signed and accepted by the involved parties.
-
E.
signedFor
Indicates that one entity formally accepted or acknowledged receipt of something on behalf of another, typically by providing a signature.
- 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_69a493c476b48190b41fc5e793171cc6 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b4e0f0d081908b888c246d001786 |
completed | March 1, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69a4b2af071c819086c374a16307dfe0 |
completed | March 1, 2026, 9:42 p.m. |
Created at: March 1, 2026, 7:41 p.m.