Triple
T34439284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Tartu |
E884052
|
entity |
| Predicate | signatoryRepresentativeOfRSFSR |
P6229
|
FINISHED |
| Object | Adolf Joffe |
—
|
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: Adolf Joffe | Statement: [Treaty of Tartu, signatoryRepresentativeOfRSFSR, Adolf Joffe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signatoryRepresentativeOfRSFSR Context triple: [Treaty of Tartu, signatoryRepresentativeOfRSFSR, Adolf Joffe]
-
A.
signedByRepresentativeOf
chosen
Indicates that an item (such as a document or agreement) has been signed on behalf of a party by that party’s authorized representative.
-
B.
signatoryDiplomat
Indicates that a diplomat is an official signatory to an agreement, treaty, or formal document.
-
C.
wasSignatoryOf
Indicates that an entity formally signed or endorsed a specific document, agreement, or treaty as a participating party.
-
D.
signatoryGovernment
Indicates that a government is a formal signer or ratifying party to an agreement, treaty, or similar binding instrument.
-
E.
foundingSignatory
Indicates that an entity was an original signer or member at the founding of another entity, agreement, or organization.
- 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_69f349c548d88190978e2a82502c03d0 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71fb1ab3881908e2f7c0e6f23db49 |
completed | May 3, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69f71cc6397881909aaad37a9daa8a7e |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 2 a.m.