Triple
T20576961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nystadsfreden |
E505242
|
entity |
| Predicate | datumUndertecknat |
P439
|
FINISHED |
| Object | 1721-08-30 |
—
|
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: 1721-08-30 | Statement: [Nystadsfreden, datumUndertecknat, 1721-08-30]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: datumUndertecknat Context triple: [Nystadsfreden, datumUndertecknat, 1721-08-30]
-
A.
firmatoDa
Indicates that something (such as a document, contract, or work) has been signed or formally endorsed by a specific entity.
-
B.
noteSignature
Indicates that one entity serves as a signature or identifying mark attached to a note created or associated with another entity.
-
C.
dateSigned
chosen
Indicates the specific date on which an agreement, document, or contract was formally signed.
-
D.
signText
Indicates that a sign bears or displays a particular textual content.
-
E.
signature
Indicates that one entity has provided an official or personal signed endorsement, authorization, or acknowledgment on or for another entity.
- 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_69e0b4b721588190993ac7b0a9be2736 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a90af3608190955d2c7950726178 |
completed | April 20, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69e59fffe1748190825e4eaa90340631 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:39 a.m.