Triple
T9505690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS-20 Saber |
E229262
|
entity |
| Predicate | deploymentRegions |
P23381
|
FINISHED |
| Object | western Soviet Union |
—
|
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: western Soviet Union | Statement: [SS-20 Saber, deploymentRegions, western Soviet Union]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deploymentRegions Context triple: [SS-20 Saber, deploymentRegions, western Soviet Union]
-
A.
serviceRegion
Indicates the geographic area or jurisdiction within which a service is provided or applicable.
-
B.
launchSiteRegion
Indicates the geographic region in which a launch site is located.
-
C.
landingRegion
Indicates the area or zone where an object or entity comes to rest or makes contact after moving or descending.
-
D.
operatesToRegion
chosen
Indicates that an agent conducts operations or provides services directed toward or within a specified region.
-
E.
endpointRegion
Indicates that one entity serves as the geographic or logical region in which the other entity’s endpoint is located or configured.
- 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.