Triple
T1454614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strategic Arms Limitation Talks |
E31369
|
entity |
| Predicate | limitedWeaponType |
P28787
|
FINISHED |
| Object | intercontinental ballistic missiles |
—
|
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: intercontinental ballistic missiles | Statement: [Strategic Arms Limitation Talks, limitedWeaponType, intercontinental ballistic missiles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: limitedWeaponType Context triple: [Strategic Arms Limitation Talks, limitedWeaponType, intercontinental ballistic missiles]
-
A.
prohibitedWeaponType
Indicates that a particular type of weapon is classified as not allowed or forbidden under specified rules, laws, or agreements.
-
B.
typicalWeapon
Indicates that the object is a weapon commonly or characteristically used by the subject.
-
C.
gunType
Indicates the specific category or kind of gun associated with an entity.
-
D.
weaponsUsed
Indicates that one entity employed or utilized another entity as a weapon in carrying out an action or event.
-
E.
weaponCategory
Indicates the classification or type of weapon to which an item or armament belongs.
- F. None of above. chosen
Provenance (4 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_69a499171a28819085b993a3ac78e363 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c57fead881909a47188ce7312406 |
completed | March 1, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69a4c47cdbd0819092022344a2f4ad7b |
completed | March 1, 2026, 10:58 p.m. |
| PDg | Predicate description generation | batch_69a4c55508948190922aee3230a4323e |
completed | March 1, 2026, 11:01 p.m. |
Created at: March 1, 2026, 8 p.m.