Triple
T665143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Westminster (1674) |
E12844
|
entity |
| Predicate | dateSignedOldStyle |
P439
|
FINISHED |
| Object | 1674-02-09 |
—
|
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: 1674-02-09 | Statement: [Treaty of Westminster (1674), dateSignedOldStyle, 1674-02-09]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateSignedOldStyle Context triple: [Treaty of Westminster (1674), dateSignedOldStyle, 1674-02-09]
-
A.
dateSigned
chosen
Indicates the specific date on which an agreement, document, or contract was formally signed.
-
B.
dateSignificance
Indicates the specific importance, meaning, or notable role that a particular date holds within a given context or relationship.
-
C.
dateOf
Indicates that one entity specifies the calendar date associated with another entity, such as when it occurred, was created, or is scheduled.
-
D.
dateGranted
Indicates the specific date on which a right, status, or permission was formally conferred or approved.
-
E.
signedAs
Indicates that an entity has signed or endorsed something using a particular name, role, or identity.
- 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_69a493355dec819098d4244b2fa34885 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49fd3d8fc8190866af5c76c08f486 |
completed | March 1, 2026, 8:21 p.m. |
| PD | Predicate disambiguation | batch_69a49d16cff881908c8d2c3fe4d1d6fb |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:36 p.m.