Triple
T342804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mutual Defense Agreement (1958) |
E6872
|
entity |
| Predicate | renewalInterval |
P5690
|
FINISHED |
| Object | typically 10 years |
—
|
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: typically 10 years | Statement: [Mutual Defense Agreement (1958), renewalInterval, typically 10 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: renewalInterval Context triple: [Mutual Defense Agreement (1958), renewalInterval, typically 10 years]
-
A.
renewalPattern
chosen
Indicates the recurring schedule or frequency with which something is renewed or repeated over time.
-
B.
isRenewable
Indicates that a resource or energy source can be naturally replenished or regenerated within a human-relevant timescale.
-
C.
locationPeriod
Indicates that an entity is associated with being at a particular location during a specified time period.
-
D.
reappointmentPolicy
Indicates the rules or conditions governing whether and how an individual can be reappointed to a position or role.
-
E.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
- 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_69a2e7951ba08190960e90823b5078f3 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eafef8c88190a5932eb2c6ac4a5d |
completed | Feb. 28, 2026, 1:17 p.m. |
| PD | Predicate disambiguation | batch_69a2e9530c98819085025efe4e04aa7e |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.