Triple
T26585931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Sistova |
E667209
|
entity |
| Predicate | confirmedStatusQuo |
P162808
|
FINISHED |
| Object | most pre-war frontiers |
—
|
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: most pre-war frontiers | Statement: [Treaty of Sistova, confirmedStatusQuo, most pre-war frontiers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: confirmedStatusQuo Context triple: [Treaty of Sistova, confirmedStatusQuo, most pre-war frontiers]
-
A.
confirmedAs
Indicates that one entity has been officially verified, recognized, or validated as being identical to or serving in the role of another entity.
-
B.
confirmedOrModified
Indicates that an existing item, state, or assertion has either been verified as correct or updated with new information.
-
C.
confirmedBy
Indicates that one entity validates, approves, or verifies the truth, accuracy, or occurrence of another entity or event.
-
D.
signedStatus
Indicates whether an entity has formally signed or approved a document, agreement, or record.
-
E.
confirmedFor
Indicates that an entity has been officially approved, scheduled, or validated to participate in, receive, or be associated with another specified entity or event.
- F. None of above. chosen
Provenance (4 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_69ee9cfb7e548190b60a9031182f5a7e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f62e4168a48190b45268f922780da6 |
completed | May 2, 2026, 5:02 p.m. |
| PD | Predicate disambiguation | batch_69f62c15952881908a5ea0c25904afec |
completed | May 2, 2026, 4:53 p.m. |
| PDg | Predicate description generation | batch_69f62d5268ac8190835dc7119353b840 |
completed | May 2, 2026, 4:58 p.m. |
Created at: April 27, 2026, 2:05 a.m.