Triple
T10923011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Организация Договора о коллективной безопасности |
E257993
|
entity |
| Predicate | basedOnTreatySignedOn |
P23330
|
FINISHED |
| Object | 1992-05-15 |
—
|
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: 1992-05-15 | Statement: [Организация Договора о коллективной безопасности, basedOnTreatySignedOn, 1992-05-15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnTreatySignedOn Context triple: [Организация Договора о коллективной безопасности, basedOnTreatySignedOn, 1992-05-15]
-
A.
treatySignedWith
Indicates that a formal treaty or agreement has been officially signed between two parties.
-
B.
treatySignedFor
Indicates that a formal treaty has been signed on behalf of, or in representation of, a particular entity, cause, or subject.
-
C.
cededByTreaty
Indicates that control or ownership of one entity was formally transferred to another entity as a result of a treaty or formal agreement.
-
D.
treatySignedYear
chosen
Indicates the calendar year in which a specific treaty was formally signed.
-
E.
treatyOf
Indicates a formal agreement or pact established between entities, typically states or organizations, defining their mutual obligations or terms.
- 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_69d6aa864ed88190818280ab6791d065 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7708e3fd881908da10f24a856364c |
completed | April 9, 2026, 9:25 a.m. |
| PD | Predicate disambiguation | batch_69d72e799f808190b6ab64fc7586a303 |
completed | April 9, 2026, 4:43 a.m. |
Created at: April 8, 2026, 9:22 p.m.