Triple
T6281653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UN General Assembly Resolution 2222 (XXI) |
E140794
|
entity |
| Predicate | dateOpenedForSignature |
P7773
|
FINISHED |
| Object | 1967-01-27 |
—
|
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: 1967-01-27 | Statement: [UN General Assembly Resolution 2222 (XXI), dateOpenedForSignature, 1967-01-27]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOpenedForSignature Context triple: [UN General Assembly Resolution 2222 (XXI), dateOpenedForSignature, 1967-01-27]
-
A.
dateSigned
Indicates the specific date on which an agreement, document, or contract was formally signed.
-
B.
openedForSignatureBy
Indicates that one entity has made a document or agreement available for others to sign.
-
C.
openedForSignature
chosen
Indicates that an agreement, document, or treaty has been formally made available for eligible parties to sign.
-
D.
agreementSignedAt
Indicates the specific time and/or place at which an agreement was formally signed.
-
E.
issuedDocumentDate
Indicates the date on which a document was formally created, released, or made officially valid by the issuing 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_69c008cd17c8819082b82d3fbeb68047 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c063dee62881908347283f16dcbe68 |
completed | March 22, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69c05608a5608190b22a1fdc4060470d |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:26 p.m.