Triple
T9505695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS-20 Saber |
E229262
|
entity |
| Predicate | keyFactorIn |
P7606
|
FINISHED |
| Object | INF Treaty negotiations |
—
|
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: INF Treaty negotiations | Statement: [SS-20 Saber, keyFactorIn, INF Treaty negotiations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyFactorIn Context triple: [SS-20 Saber, keyFactorIn, INF Treaty negotiations]
-
A.
keyFeature
Indicates that something is a primary, distinguishing, or most important feature of an entity.
-
B.
key
chosen
Indicates that one entity functions as a key (literal or metaphorical) that unlocks, enables access to, or provides a crucial solution or control over another entity.
-
C.
keyOfWork
Indicates that one entity specifies the musical key in which a particular work is composed or performed.
-
D.
keyObservation
Indicates that an entity is a primary or crucial observation about another entity, typically highlighting a central finding, feature, or insight.
-
E.
keyPassage
Indicates that a specific passage or excerpt is identified as especially important, central, or representative within a larger text or discourse.
- 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_69ca847611c48190a28c028644198c75 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9852b7e48190a8f69cbde10d2858 |
completed | April 1, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69cca567ca448190bf4bcce8ce7dd54f |
completed | April 1, 2026, 4:56 a.m. |
Created at: March 30, 2026, 7:57 p.m.