Triple
T3903860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Geneva Accords of 1988 |
E90557
|
entity |
| Predicate | stipulatedWithdrawalPeriod |
P20300
|
FINISHED |
| Object | 9 months |
—
|
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: 9 months | Statement: [Geneva Accords of 1988, stipulatedWithdrawalPeriod, 9 months]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stipulatedWithdrawalPeriod Context triple: [Geneva Accords of 1988, stipulatedWithdrawalPeriod, 9 months]
-
A.
withdrawalNoticePeriod
chosen
Indicates the required amount of time that must pass between giving notice and executing a withdrawal.
-
B.
removalPeriod
Indicates the time span during which something is taken away, deleted, or otherwise removed from availability or consideration.
-
C.
timeBetweenAnnouncementAndTermination
Indicates the duration of time that elapses between when something is officially announced and when it is subsequently terminated.
-
D.
withdrawalDate
Indicates the date on which a withdrawal action occurs or is recorded.
-
E.
hasWithdrawalClause
Indicates that an agreement or contract includes a provision specifying how a party may withdraw or terminate their participation.
- 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_69aed95d315881908cbf1bf4a7215fbf |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef1abe2dc81909c18aeae9b286898 |
completed | March 9, 2026, 4:13 p.m. |
| PD | Predicate disambiguation | batch_69aee75cff148190b6d5979d17fae085 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:22 p.m.