Triple
T25930819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sovetsk, Russia |
E653433
|
entity |
| Predicate | treatySignedThere |
P8839
|
FINISHED |
| Object | Treaty of Tilsit (1807 between France and Prussia) |
—
|
NE NERFINISHED |
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: Treaty of Tilsit (1807 between France and Prussia) | Statement: [Sovetsk, Russia, treatySignedThere, Treaty of Tilsit (1807 between France and Prussia)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: treatySignedThere Context triple: [Sovetsk, Russia, treatySignedThere, Treaty of Tilsit (1807 between France and Prussia)]
-
A.
treatySignedFor
Indicates that a formal treaty has been signed on behalf of, or in representation of, a particular entity, cause, or subject.
-
B.
signedTreatyAt
Indicates that an entity formally entered into and endorsed a treaty at a specific location.
-
C.
treatySignedWith
Indicates that a formal treaty or agreement has been officially signed between two parties.
-
D.
treatySignedPlace
chosen
Indicates the location where a treaty was formally signed or concluded.
-
E.
wasSignatoryOf
Indicates that an entity formally signed or endorsed a specific document, agreement, or treaty as a participating party.
- 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_69e7ab3eb9b881909c1390690551f868 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f627aedf548190bc9f53c8a2d67b50 |
completed | May 2, 2026, 4:34 p.m. |
| PD | Predicate disambiguation | batch_69f623a4e1048190bbb8dd1253fdcee9 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 22, 2026, 8:36 a.m.