Triple
T23721844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | China and North Korea |
E586165
|
entity |
| Predicate | treatyRenewalPattern |
P5690
|
FINISHED |
| Object | periodically renewed |
—
|
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: periodically renewed | Statement: [China and North Korea, treatyRenewalPattern, periodically renewed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: treatyRenewalPattern Context triple: [China and North Korea, treatyRenewalPattern, periodically renewed]
-
A.
treatyRenewal
Indicates the extension or re-establishment of an existing treaty’s validity or terms between parties.
-
B.
treatyPeriod
Indicates the span of time during which a treaty is in force or considered applicable.
-
C.
renewalPattern
chosen
Indicates the recurring schedule or frequency with which something is renewed or repeated over time.
-
D.
renewalTerm
Indicates the length or conditions of time for which an agreement, contract, or subscription is extended beyond its initial term.
-
E.
treatyAfter
Indicates that a treaty or formal agreement was established after a specified prior event, condition, or relationship between the entities.
- 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_69e24906fb108190a6898751e46bdc11 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b91177c08190bea6e62ed13e2495 |
completed | April 29, 2026, 7:53 a.m. |
| PD | Predicate disambiguation | batch_69f155e4b1148190836ede4741dcb888 |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 7:02 p.m.