Triple
T669190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chemical Weapons Convention |
E12933
|
entity |
| Predicate | openedForSignatureOn |
P7773
|
FINISHED |
| Object | 1993-01-13 |
—
|
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: 1993-01-13 | Statement: [Chemical Weapons Convention, openedForSignatureOn, 1993-01-13]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedForSignatureOn Context triple: [Chemical Weapons Convention, openedForSignatureOn, 1993-01-13]
-
A.
openedForSignature
chosen
Indicates that an agreement, document, or treaty has been formally made available for eligible parties to sign.
-
B.
hasSignFor
Indicates that one entity displays, bears, or provides a sign, symbol, or notice that represents, directs attention to, or gives information about another entity.
-
C.
signedAs
Indicates that an entity has signed or endorsed something using a particular name, role, or identity.
-
D.
signedDuring
Indicates that an agreement, document, or contract was signed within a specified time period or during a particular event.
-
E.
dateSigned
Indicates the specific date on which an agreement, document, or contract was formally signed.
- 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_69a493355dec819098d4244b2fa34885 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49ffbe09881909b547a52a6b34c7f |
completed | March 1, 2026, 8:22 p.m. |
| PD | Predicate disambiguation | batch_69a49d18942c819083b3d1887e505900 |
completed | March 1, 2026, 8:10 p.m. |
Created at: March 1, 2026, 7:36 p.m.